- 21 June 2023 (30 messages)
-
-
The problem I see here are for scalability. Even getting rid of scammers using this it´ll be complex to manage and centralized, even if it´s a trusted party it´s not optimal IMO. CMYK had to do over 50 refunds and it was on a hype wave of new users that wasn´t even 1% Opensea nº of trades. And the refunds came by users frontrunning each other to get their assets.
-
Assets aren’t stuck in Hiro. Can import to Freewallet.
-
Yeah very true
-
yes, but are people that dont want to do it
-
I heard Jdog mention incorporating a VM layer, could this be the UI to solve this issue?
-
-
Crap this doesn’t even solve the problem… even with this a scammer can still transfer when they see the tx hit the mempool. The only difference is they need to build the tx manually with another utxo as the input.
-
Wouldn’t even require that
-
Were you thinking like a 2 of 2 multisig dispenser address?
-
Might be a good revenue stream for the escrow agent
-
Isn’t that basically open bazaar
-
Nothing that fancy. You generate an address and provide it to me. I set up the dispenser on your address. Beside your generated addresses is a picture of you with a checkmark. For the service you're providing, you take a cut and send me the balance.
-
Dispenser daddy
-
yes
-
-
same!
-
Yeah its not really about one or the other. Both could, presumably, exist. Though these "trusted intermediary" dispensers would require zero protocol changes, so I could see them being built first
-
- 22 June 2023 (50 messages)
-
Big announcement: SRC-20 has been retooled from the ground-up by the SRC-20 devs to avoid using Counterparty numeric assets for DEPLOY/MINT/TRANSFER functions. It goes live at block-height 796,000 which is on June 26th. Bitcoin "art" Stamps will continue in their current form, for the forseeable future, as they have not been deemed "spam".
-
SRC-20 ANNOUNCEMENT:
The SRC-20 devs are happy to announce that Transfer will go live at block height: 796,000!
What this means: A new reference client wallet is currently being beta-tested by community members and will allow SRC-20 Transfer functionality. Longer term, we expect Hiro wallet to also support full SRC-20 capabilities.
We thank you for your patience, as it was essential that we get things right! Expect a further announcement closer to the launch. -
-
-
-
So I've been working together with @blockjack8 to develop a perfect FAQ for BTCpay for users using Freewallet v0.9.23. He and I dug into the forums, github, asked in dev chat and counterparty chat about this process. We are trying to hash this out for users to make it the most smooth process and easy for anybody new to Counterparty. Both Angel and I haven't used BTCpay before, so we both thought we would test the process.
Angel threw up a test BTC/RAREAIRDROP market and we got some help early on from @al_fernandz , in which Al successfully filled his BTCpay order here: https://xchain.io/tx/2428927
It was Al's experience that this simply "filled automatically" when he made sure to keep Auto BTCpay in the ON setting when making the BTCpay order. Which was completed and filled. He is also using v0.9.23.
Angel and I also then tried to do the same process, but our orders never automatically filled even though the market had open sell orders that should have automatically matched for us to buy with btc. It was strange because we did not have the same experience as Al.
I went even farther to try filling the order on the Auto setting (https://xchain.io/tx/2429910) and the Manual setting which I expected some sort of popup while keeping Freewallet open (https://xchain.io/tx/2429937). No fills. No popup at that time.
I took a break after many hours of nothing "automatically happening" and the next day I would eventually close and restart my Freewallet to see these two popups:
"Enable Auto-BTC pay?" - which it then asked for my password (just the one I created in Freewallet to lock my account, which is normal for unlocking Freewallet for other functions)
Then it popped up a statement "Auto BTCpay is now enabled and any order matches for BTC will be automatically paid"
So I thought, okay, why not try again? I used Auto BTC pay setting again assuming it should work now (https://xchain.io/tx/2430021). Still no luck. No order matches like Al's tx did , still not "working" from my user experience. Even stranger, Angel nor Al every saw these "Auto-BTCpay" popups.
In Angel's and my experience, BTCpay function is not working correctly for us in v0.9.23
So Al recently did a little experiment today. He tried (as Angel and I did) putting in a BUY order for buying 1 RAREAIRDROP for 0.002 BTC (as it SHOULD match the sell/buy list already open on the RAREAIRDROP/BTC market) - https://xchain.io/tx/e3e9b1ccaa1f1cc71478651e0e660eda98d52a64809190286158e3b7b686a1a1
Al also then put in a SELL order for 0.001 for 5 RAREAIRDROP to test the other direction of the trade - https://xchain.io/tx/ff6408b1da973a7f18256d391d0bc658b08d53329522f80f1e8dd884b96035a0
Now it looks like neither of the two new tx's from Al have matched correctly. So now I'm gonna stop wrapping my head around this and look into making other FAQ's for other functions. This will need to be sorted out before Angel and I can successfully write an FAQ on this subject.
Please anyone that is very familiar with BTCpay can you check this function out in v0.9.23? @jdogresorg , @c0rnh0li0 , @hodlencoinfield
Anything I can do from my end txs/debug I will gladly do but with my technical knowledge I am at an absolute standstill and cannot test or use this function. -
thanks for putting all our efforts into this writting
-
not seeing any order matches on these orders... in order for auto-btcpay to work, order matches have to happen.... just mentioning it so your aware this is NOT a freewallet issue, but rather some question about order matching within the CP DEX engine... so if your digging, dig into CP and order matching, not freewallet functionality... AFAIK auto-btcpay works fine for years as long as wallet is open and order matches take place.... if CP does not do order matching, then wallet cant detect order match and send btcpayment....
-
Al's first tx was order matched https://xchain.io/tx/2428927
-
I believe that @jp_janssen spent some time digging into the DEX and btc order matching at one point (could be mistaken)... and thought he discovered that in some case you needed to pay over by 1 satoshi or something for the order match to happen.... cant remember exactly what the "gotchya" was... but do recall someone having issues like this in past, where orders appear like they should match on exact price, but they do not..... TLDR, any issue here is a DEX order matching issue and not an issue with freewallet... best to get someone who can dig into dex a bit more than me.
-
yup... need someone with time to dig into exactly why one order matched and one didnt
-
but if we are going down this rabbit hole... lets DOCUMENT the findings... so we dont waste time having this conversation again in another month, 3 months. 6 months when someone else has same issue 😛
-
appreciate you digging into this and trying to build out a FAQ... much awesome 🙂
-
Just let me know and @blockjack8 and I will make sure the process is added to the FAQ
-
-
understandable... you've done a bunch of great work! kudos sir 🙂
-
I saw this "Active orders and BTC Pay
Note that BTC Pay is available only in the CLI and API.
If your order was to sell BTC, you will still lose the fee_provided (by default 1% of BTC order size). This is done so that the DEx does not get flooded by orders from users who are not serious about concluding their matched orders with payments.
If your order was to sell XCP or other Counterparty-based token for BTC, you will lose 0.002 + 2 * 0.00078 BTC (one transaction + 2 escrow fees)." here https://forums.counterparty.io/t/when-is-a-dex-order-considered-active-and-how-can-i-cancel-it/1180When is a DEx order considered "active" and how can I cancel it?If you place order on the DEx, it is not considered active because it first need to enter the blockchain, which may take couple of minutes. Once that happens, you will get a notification that your order is active and you will be able to see that in your wallet’s history (select correct address from drop down list in History pane). At that time you will also be able to see your offer (order) under Exchange > Open orders. As long as your order has not been matched, you can click Cancel to...
-
not sure if still applying and if it has to do something with this issue we are experiencing.
-
what was the btc amount for your test orders?
-
0.0002 BTC
-
this are the orders https://xchain.io/asset/RAREAIRDROP#orders
-
all of them to buy or sell at that price are from our tests
-
ahh i think thats it
-
i think the 0.001 is minimum amount to hit the minimum fee threshold, although i dont think you “lose” it you just pay the difference in the btcpay tx
-
you only lose it if you don’t complete the order
-
you could click around my old btcpaymarket repo just to see the general workflow
-
ahá
-
stop being poor you all
-
GitHub - loon3/btcpaymarket: Buy and Sell Counterparty (XCP) Assets with Bitcoin
Buy and Sell Counterparty (XCP) Assets with Bitcoin - GitHub - loon3/btcpaymarket: Buy and Sell Counterparty (XCP) Assets with Bitcoin
-
old bad code but might be helpful
-
Can confirm in my orders, the one that worked was beyond that amount
-
the ones below didn't 🫡
-
Interesting. So I should add in the FAQs that this won´t work for buying below that pice.
-
and why did you pay more in the first one? because you bought many tokens?
-
ah wait, fees
-
because mine fail and the one from Davesta too and we just tried to buy 1
-
I thought it was amount
-
my bad
-
no, nvm, fees were also below 0.001
-
fees were in fact below 0.001 in the three cases
- worked: https://xchain.io/tx/2428927
- didn't work: https://xchain.io/tx/e3e9b1ccaa1f1cc71478651e0e660eda98d52a64809190286158e3b7b686a1a1
- didn't work: https://xchain.io/tx/ff6408b1da973a7f18256d391d0bc658b08d53329522f80f1e8dd884b96035a0 -
if this is the case and the issue is not Freewallet, but the Counterparty function at a basic level, then this requirement of 0.001 should be fixed. There should be no reason you have to spend 0.001 btc to have the function operable from a users perspective (dont know what the code needs)
-
im not opposed to it, would be a consensus change
-
-
start by creating a new discussion here https://github.com/CounterpartyXCP/cips/discussionsCounterpartyXCP/cips · Discussions
Explore the GitHub Discussions forum for CounterpartyXCP cips. Discuss code, ask questions & collaborate with the developer community.
-
-
Remove Armory from fednode stack · CounterpartyXCP/cips · Discussion #94
Armory is still installed when a "counterwallet" fednode is spun up, and takes up a TON of disk space. The armory project stopped getting updates in 2016 and is rarely used by anyone. htt...
-
Add `proxy` fednode install mode · CounterpartyXCP/cips · Discussion #95
I believe the base install should be the minimum amount required to run a counterparty instance, and not include additional components which are not necessary. Currently xcp-proxy and http-addrinde...
-
Lower Requirement to Trigger BTCpay Order Match from 0.001 BTC to Something Lower · CounterpartyXCP/cips · Discussion #96
Below is a test process I used, along with help from @Blockjack8 and @al_fernandz to try to use the BTCpay function using Freewallet v0.9.23 and we found orders were not matching with BTC orders un...
-
-
I just checked counterparty-lib code... we lowered the min_btc_quantity value to 0.00001 BTC a while ago
https://github.com/CounterpartyXCP/counterparty-lib/blob/master/counterpartylib/lib/messages/order.py#L443-L446
Here is the PR with the update
https://github.com/CounterpartyXCP/counterparty-lib/pull/1070
So... if we are stuck at 0.001 still, seems this is could be a bug.
Can someone pls dig into this and verify... testnet uses same order code... so can test on testnet easily.counterparty-lib/counterpartylib/lib/messages/order.py at master · CounterpartyXCP/counterparty-libCounterparty Protocol Reference Implementation. Contribute to CounterpartyXCP/counterparty-lib development by creating an account on GitHub.
- 23 June 2023 (3 messages)
-
Yes, try looking for it in counterparty forums or github issues. Must be like 5 yrs ago.
I will not have time to dive into this myself the next two weeks.
I encorage using testnet and document cases where the DEX does not work as expected. -
Regarding btc_min - is this a wallet thing or a protocol requirement?
-
Protocol requirement
- 25 June 2023 (6 messages)
-
@jdogresorg fyi this asset is showing on xchain as being in block 780,318 correctly...
https://xchain.io/search?query=A1609866718358670800
however it does not show up in the query for that block:
https://xchain.io/block/780318
it does show up in the CP messages and issuances table correctly in 780318. not sure if your block query is supposed to show all messages for a particular asset, but i don't see it in any of the block queries for 780321 or 780773 and it doesn't appear to be impacted by a reorg? -
Hi Dev, my team is trying to built a simple front end UI that display all STAMPs Assets on a given BTC address. Looking for a Devs that can assist me with this. Thank you.
-
-
I see. I was told that since STAMPs are counterparty assets that this would be a place to ask questions.
-
Please take it to Stamps chat. There is an API you can plug into. This isn’t really a Counterparty protocol type issue
-
@MeganOanh DM me I’ll pass along webservice details
- 26 June 2023 (1 messages)
-
Joined.
- 29 June 2023 (2 messages)
-
Hello beautiful Counterparty Devs, I recently took a shot at writing a Freewallet FAQ and was wondering if I could get some feedback and a critical eye to the functions explained. Getting this looking good will absolutely be a great education to the user community and I would love any feedback on it: https://github.com/jdogresorg/freewallet-desktop/discussions/138Freewallet FAQ 2023 v0.9.23 - Write Up - Draft #5 · jdogresorg/freewallet-desktop · Discussion #138
It has been asked for and needed for some time now, so I present the - Draft 5 of the Freewallet FAQ I used Freewallet Desktop v0.9.23 to write this up with the help of the Counterparty Forums, Cou...
-
my feedback is in our dms .. hopefully I will get to respond on github next week