I found some py scripts when i looked into this last year. I didn't go further since they require bitcoin core. With fed node you should be good.
Dont remember exactly where i found the scripts except they were on github, possibly linked to from counterparty talk.
- 01 July 2022 (11 messages)
-
-
reading around on this it seems these multisig redemption transactions are non standard and therefore can't be broadcast and would need to be fed to a miner out of band ... but I could be wrong ? -
I did successfully retrieve dust in 2017.
If such tx's later have become non-standard i dont know.
If they have, it's a pity also for the wider bitcoin ecosystem. Removing dust helps clean up the utxo set. -
https://www.blockchain.com/btc/tx/1b0f92a037bf9b4508b3937f07121cfe1dd147f1a867acb0444e11c514f5bc69
Here's an example. I swept dust in April 2017. Unfortunately paid a high fee (34 sats/b) and half went to miners.
There was a fee crisis back then, so i hurried to do it before it would become uneconomical to sweep.
In retrospect the wrong decision. Today it should be possible at 1 sat/byte .. if such tx's haven't become non-standard 🙊Blockchain.com Explorer | BTC | ETH | BCHThe easiest and most trusted transaction search engine and block explorer.
-
that's encouraging to read, I was going from a 'sipa' comment from 2015 on github that's says since v0.10 such transactions are non standard unless first pubkey is valid when discussing counterparty multisig
-
This is very cool. But you should be able to repeat this if you use the same bitcoin version from back then, right? -
Two concerns
1. The website to construct redeem tx is down.
2. If the tx has become non-standard, yes i can sign with the old version, but updated nodes would reject it. -
Redeem unspent outputs and multisig dust - Coin Sweeper
Not only helpful for Mastercoin and Counterparty, but for Bitcoin users in general, this tool allows to reclaim perceived fees by locating unspent outputs.
-
I emailed him a few years back, but no reply. Our best shot would be to try again. Maybe raise a bounty.
-
-
I have tried today using one of my multisig dust outputs, using bitcoin-cli createrawtransactionI i specify in the vin part the funding txid, vout, amount and I can specify the address and amount to pay in the vout part ... but when I verify the returned hex using coinb.in it does not show as being a multisig transaction, I think I am missing the redeemScript for the vin part when constructing the redeem transaction ?
- 02 July 2022 (7 messages)
-
When I sign my createrawtransaxtion hex tx with coinb.in I get a
''mandatory-scrpit-verify-flag-failed signature is found in scriptCode (code 16)' error
does anyone know how to construct the transaction so I don't get that error ? or does anyone know if that is the error expected due to tx being non standard? -
Have you tried https://gist.github.com/sorce/c60dfaac06d19842edfd5b7e2804ddc5 ?Sweep utxos - https://counterpartytalk.org/t/public-passphrase-sweepable-multisig
Sweep utxos - https://counterpartytalk.org/t/public-passphrase-sweepable-multisig - sweep_funds.py
-
Public Passphrase & Sweepable Multisig
The address 1God8QecZZVs2jA3z5tZaAKV5gwLYtfaQv has a publicly known passphrase: childhood confusion large many bridge guy reveal press treat soul murder crush About 20 cent worth of BTC are stuck in redeemable multisig. Afaik there is no tool to redeem these funds. Whoever first finds a way can cash in these multisigs. Another public passphrase is love love love love love love love love love love love love I know 20 cent is not much of an incentive but I encourage everyone to continue playin...
-
maybe its possible to modify the code and try with feeding it teansactuon ids
-
I am thinking yes use txid and getrawtransactiom with the bitcoincore I am currently running .. no need to use the searchrawtransaction rpc call if you know the txid(s) that you want to spend from
we can search all issuance transactions by an address in çounterparty and then see if description >=46 to see if we created multisig dust that needs spending this way
I see also see scriptSig mentioned in the example code which helps - 05 July 2022 (27 messages)
-
I have using bitcoin-cli managed to spend a 7800 satoshi bare multisig output to myself
-
We at least now know it is possible to spend the 7800 bare multisig outputs .. we now just need a nice UI
I used a modern version of bitcoin core .. no need for the older version -
thanks for the links and advice
I am now going to try building a transaction that has multiple inputs from multiple previous multisig transaction outputs ... so it will consolidate say 10 x 7800 satoshi outputs into a single utxo -
How can this asset (single issuance) without an enhanced asset info json link (or even a description) has an image and thumbnail? https://xchain.io/tx/1810
-
The dust limit is currently 543 satoshi , why is 5430 the amount used in p2sh? it seems we are paying 10x the required amount
-
it used to be 5430 -
but also i believe that dust is being used as tx fee for p2sh encoding
-
would have to ask javier to clarify
-
yeah .. would be nice to pay at the rate of 1 sat per byte for the encoding
-
from what i understand, that p2sh output is like a pre-image for the actual counterparty message data which is included in the input signature when that output is spent
-
so by making it smaller, you would probably need to include another input to spend it making the overall tx cost higher
-
I need to study those transactions a bit more to fully understand what you just said but yeah lowest tx fees is the aim and people can always pay more if in a hurry
-
for sure, but its also important to consider the cost of spending a dust output in relation to the size
-
indeed .. I just reclaimed 10x7800 satoshi from various multisig outputs from 5 different transactions .. I paid just 1.3 sats per byte, so I have got to wait for a confirmation but thats OK am in no rush
-
de dusting is worth the effort from time to time ..and if you can time it right e.g. when the mempool is empty then there won't be much of a delay even at 1 sat per byte
-
Yeah for sure, easy to get spoiled with a near empty mempool
-
I would say de-dusting should be encouraged! We need to be responsible users of bitcoin, which has been optimized for small/cheap pruned nodes. The block space is an open market, but the utxo set should be used responsibly
-
yeah and using rbf is advised as there are sone nodes out there that hold onto transactions in the mempool for a very long time ... I had one tx that took around 30 days to get a confirmation
-
Bump. Anyone can help me understand this?
-
if you pay JDog/Xchain for a project listing the project has a json file that xchain accesses over HTTP that provides Xchain with asset info such as image
-
If this is the case, then other counterparty /counterblock nodes won’t have any reference to these images. Correct?
-
not necessarily
-
there wasnt an accepted image hash/link scheme for older counterparty assets
-
so we relied on centralized servers to “show us what the assets look like”
-
Ok but in the node I am setting up there won’t be these references, right?
- 06 July 2022 (40 messages)
-
Correct. Counterparty has onchain metadata through asset description and broadcasts BUT does not interpret these.
It's up to 3rd parties to make sense of the data. I guess the idea was to keep it open so standards could emerge (?)
In many cases there is no onchain data (or something like 'trading card' only). Then of course an editorial choice whether a specific image represents the token. -
Got it, thanks! You mentioned “onchain metadata through asset description and BROADCASTS”, what do you mean by broadcasts here? Can assets reference a broadcast? I was thinking about this since broadcasts seem to have “unlimited” text length…
-
The data is there. Just make sure it's from the issuer address and the asset is mentioned.
One sec, will provide example -
https://jpjanssen.com/timeline/counterparty.html?asset=SEBUH
I made the script look for broadcasts where issuer mentions own asset (ADD INFO) and where other addresses mention it (MENTION) -
Here's a recent example https://jpjanssen.com/timeline/dogeparty.html?asset=DOGEOLITH
Hash, extra details in a broadcast -
Is there a xchain equivalent for dogeparty?
-
dogeparty.xchain.io
-
You did this?? Fkn cool music 🔊
-
How can I see the broadcast?
-
Thanks!
-
Click the timestamp, you'll see it on xchain
-
Very cool stuff, thank you for showing me all this 🤯
-
Impressive! I'm relieved it's still possible to redeem dust.
Do you have to run a full node to construct the tx? Or maybe it's possible with public api's? -
You need to get the full raw transaction that contains the dust outputs to get from it the script hex that's used when signing the spend .. I guess thats possible with a public api ... I then used Bitcoin core to sign the spend tx, I would not advise using private keys with someone else's node, it could be signed with a pruned node using signrawtransactionwithkey command
-
With the redeem.bitwatch script it was possible to sign with counterwallet. Only address shared with script, not privkey.
I guess it would be possible to sign your tx too with counterwallet or freewallet? -
I am not sure, would need to try it with counterwallet
I was unable to sign my tx with coinb.in as there was no way to pass the scriptsig hex whilst signing which was why I used bitcoin-cli to sign -
You can sign txs pretty easily with bitcoinjs-lib
-
I am thinking Peter Todd's python bitcoinlib is gonna be an easy way to trawl the blockchain to find multisig dust txs we can then reclaim .. bitwatch being gone and btcdraks addrindex being obsolete means a modern solution is needed
we can search for transactions that pay themselves at the address in question and have at least 2 multisig outputs of 7800 satoshi -
that would be great
-
Once we have a list of txids/utxos we wish to spend from then can work out how best to construct and sign the spend to self reclaiming tx
-
yea then people can check their address and see how much they could potentially claim
-
yeah that would be a good start .. creating a tx they can then take and sign with a bitcoincore node the next step and finally giving people ability to sign in their browser perhaps the last step
-
WTB 1 PEPEDINHO
@ 4000.00000000 PEPECASH
--
Price: 40 USD order -
I had to hide it in pepe.wtf for not feeling that constant hope of bargain -
Word
-
What’s the issue?
-
-
i think this is an xchain artifact
-
-
-
people trying tho lol
- 07 July 2022 (2 messages)
-
This post is so helpful 👏 -
(I'm a little late on messages because my telegram muted the discussion...)
- 08 July 2022 (2 messages)
-
should be fixed now.... the data displayed on xchain did not match the order in CP... I've written a fix_order_status.php script which loops through all open orders and checks their status in the CP database and updates accordingly.... this and a bunch of other orders like it have been fixed 🙂 -
- 10 July 2022 (34 messages)
-
One of the guys in danks was sent something, however it doesn't show in his wallet.
The tx however shows valid -
-
Any ideas what could be the issue?
-
He has both mobile and desktop freewallet
-
Same issue on both
-
what wallet is he using?
-
he has just over 1k assets and there is an API limit of 1000 results that affects some wallets
-
It's freewallet desktop and mobile
-
Arnt the assets loaded alphabetical?
-
should be
-
Not the latest version of freewallet because he can't seem to update it
-
probably freewallet mobile is what he’s using, which hasnt been updated in a while
-
It's on both desktop and mobile
-
On xchain too if you search his waller holding
-
oh weird
-
You see the send in
-
well that could be it
-
acdtually
-
No send out
-
if freewallet uses xchain API
-
and xchain isnt showing it
-
xchain has its own db
-
maybe it had a hiccup
-
i can call balances from counterparty-lib
-
Should he raise a ticket or will this rectify its self in the not too distant future
-
no harm in creating a github issue
-
but if its not showing as a holder on xchain then thats gotta be the problem
-
Yh you can see the send to him and the asset recieved was valid but no sends out and his balance doesn't show it
-
I will get him to raise a ticket
-
I see counterparty used to create 10860 satoshi outputs using a 1 of 2 bare multisig where the first part is the users pubkey and the second part counterparty data, so that's 2 different multisig schemes that have been used that create unspent cobwebs .. are there any others?
- 11 July 2022 (23 messages)
-
this looks relevant
-
-
found commented in the counterparty-lib config file next to the multisig dust output size variable
-
messing around with reducing dust limits in CP..... should hopefully have some good updates in a few weeks 🙂
-
thanks for the link I will take a look.
my python script is finding the multisig outputs matching my public key just fine .. but the searching is slow as trawling through each and every transaction in each and every block takes time.
My counterparty node almost syncd counterparty then it's just counterblock to go -
ugh counterblock is a pain....
-
you might want to just dump a list of transaction hashes for your specific address, then just loop through the specific transactions and get the tx information..... should be much faster than looking through every transaction for your specific address, etc.
-
yeah where can I get a list of issuance and broadcasts.. or just a dump of all transactions by an address easily? .. I don't want to just hammer xchain api n get blocked
-
you can query that directly in counterparty API via the get_{table} API calls
-
ie.... get_issuances and get_broadcasts... sec... getting example
-
a list of 5000 txs to check is better than 500,000 blocks
OK cool will keep my sync going and look forward to querying my node when its ready -
get_issuances example
-
-
Request
-
{
"method" : "get_issuances",
"params": {
"filters": [{
"field": "source",
"op": "==",
"value": "1JDogZS6tQcSxwfxhv6XKKjcyicYA4Feev"
}],
"order_by":"block_index",
"order_dir": "DESC"
},
"jsonrpc" : "2.0",
"id" : 0
} -
thanks yeah that's what I need to do
-
same format for get_broadcasts... just change from get_issuances to get_broadcasts
-
-
also might want to just consider dumping a list of all transactions for a given address.... not just issuances and broadcasts (could be some dust caught in other txs as well)...... check out this API call https://www.blockcypher.com/dev/bitcoin/#address-endpointBlockchain Developer API for Bitcoin, Ethereum, Testnet, Litecoin and More | BlockCypher
Build blockchain applications easily with our web APIs and callbacks. High throughputs, linear scaling, low-latency. Over 99.99% uptime with no single point of failure.
-
shouuld return you a list of all transactions for a given address.... you can then loop through the transactions and request info on each tx using tx_hash
-
-
anyway... should hopefully get ya started 🙂
-
🙏
- 12 July 2022 (22 messages)
-
The OP_Return Wars of 2014 – Dapps Vs Bitcoin TransactionsAbstract: In this piece we explore why Dapps are typically built on Ethereum rather than Bitcoin, which takes us all the way back to March 2014. We examine a debate about whether and how a Dapp pro…
-
Counterparty, the zombie protocol
-
we should do a collection on this "CP the undead"
-
yeah counter party still uses multisig .. you would expect bitmex to know that
-
Mostly we use op_return, but yes, in some cases (like issuances where we need to encode more data than we can fit in an OP_RETURN) we use other encoding methods like multisig
-
yeah . ipfs is a nice way to store json/images and arweave gets some use too .. fakerares hosted .jsons are long enough to trigger multisig encoding too
-
Things should work out. It is amazing that the mempool clears constantly. And to achieve this, some very hard stances were needed. But transactions are needed for the long term sustainability of the network. Today with a much mature market, the right people will be attracted to Counterparty
-
Yup… and once we get a VM, the sky is the limit…. Plus got some other updates that will make cp much cheaper to do sends and issuances
-
Bassmint.wtf we just launching this music site officially today
-
-
Fake asf
-
Trying to load on my phone the page loads twice then I get this
-
Same when I try to load directly in chrome
-
-
Looking Into it now
-
-
Weird it’s working on my end in safari
-
And working for another person that just checked
-
works on desktop on chrome fine... but not on mobile chrome for me
-
Clearing cloud fare cache now
-
BASSMINT.WTF
Music NFTs Community on Bitcoin. Claim your independence with your music today!
-
Here’s the telegram we just launched if anyone interested
- 13 July 2022 (5 messages)
-
My counterblock sync is VERY slow, I’ve had it for weeks and based on the progress it still has weeks left. Is this normal?
-
that's not right eh ..
-
Thanks .. I can now search upto 2000 transactions on a address looking for multisig dust in seconds
-
counterblock is old and slow.... tho it should not take weeks to make progress, should spin up pretty quick.... addrindexrs and counterparty parsing are what takes most of the time... counterblock should be pretty fast to come up after counterparty is fully synced
-
Ok thanks for the replies, definitely something is wrong then. Will look into it…
- 14 July 2022 (35 messages)
-
Something must be wrong with my setup. Everything except counterblock is synced. And I just restarted counterblock from scratch even deleting the mongo database. And in this new attempt, the logs start by showing this repeated error:
counterblock_1 | INFO:startup: Starting up counterparty block feed poller...
counterblock_1 | INFO:startup: Starting up RPC API handler...
counterblock_1 | WARNING:blockfeed: counterblockd database app_config collection doesn't exist. BUILDING FROM SCRATCH...
counterblock_1 | WARNING:util: Bad status code returned: '503'. result body: '{"code": -32000, "message": "Server error", "data": "Counterparty database is behind backend."}'. -- Waiting 3 seconds before trying again...
counterblock_1 | WARNING:util: Bad status code returned: '503'. result body: '{"code": -32000, "message": "Server error", "data": "Counterparty database is behind backend."}'. -- Waiting 3 seconds before trying again... -
so your counterparty DB is not fuly syncd .. you need to get bitcoin to the chain tip .. then addrindexrs to the tip .. then counterparty to the tip and then counterblock will sync
-
I have seen it synced all this time… and now i was only going to double check… and you are right! Counterparty is not synced at the moment. Wtf lol my bad. Let me try it later after being 100% sure everything is up to tip before starting it…
-
I used 4 x terminal windows and the 'fednode tail service' command to watch it from all angles .. keep a tab of mempool.space open too to see current blockchain height
-
Ok now it is progressing quickly. The main difference I notice is that now mongod is between 5-30% cpu. It used to be above 90% always
-
I notice bitcoin core is depreciating the 'address' data in the vout section of a getrawtransaction rpc call and in the decoderawtransaction rpc call ... so the dust finding script i have is gonna struggle to *ensure* unspent dust is yours with just an address to work from .. do you think its reasonable to ask users to supply pubKey or is that just too confusing?
if privateKey is supplied then publicKey can be calculated but if only address is supplied then unless I am mistaken it can't be walked backwards to Public Key can it?
I guess it can assume its yours but would be nicer to ensure it is -
Private key is needed to sign .. so rather than a python script perhaps a web based javascript solution with counterparty seed support is best solution .. and like RPW does keep the secret (seed) client side in a local.storage object is the way to go
-
As long as the address has spent any coins the public key will have been revealed, you should be able to grab it from any Tx from that address
-
ah yes of course .. I will look to get pubkey from a previous spend by an address
I am still thinking a javascript version with counterparty seed support is a good idea as that will allow people to de dust all the counterwallet addresses they possess -
I would be wary myself of providing a private key or 12-word passphrase into a web app to sign….. the old tool just provided an unsigned tx which users could copy and paste into a wallet to sign and broadcast…. I would suggest you do the same…. Freewallet can sign transactions n broadcast…. Could prolly even make a clickable link to open freewallet and pass the unsigned tx to the wallet to be signed.
-
I totally respect that.. It would be open sourced .. RPW is not open source and is used by a lot of folk
-
but will also do a version that create unsigned raw tx
-
would be cool to be able to click a link and send tx to freewallet to sign
-
the user could self host on 127.0.0.1 if they want to use the seed version .. its all good
-
Cool on open sourcing it…. Can prolly host direct on GitHub pages so ppl know the code that is running is the same as in the repo…. Here is an example
-
GitHub - jdogresorg/counterparty-mpma-send-tool: Counterparty Multi-Peer-Multi-Asset (MPMA) Send tool
Counterparty Multi-Peer-Multi-Asset (MPMA) Send tool - GitHub - jdogresorg/counterparty-mpma-send-tool: Counterparty Multi-Peer-Multi-Asset (MPMA) Send tool
-
GitHub pages site : https://jdogresorg.github.io/counterparty-mpma-send-tool/
-
This may interest you https://github.com/jdogresorg/freewallet-desktop/blob/master/uri-schemes.htmlfreewallet-desktop/uri-schemes.html at master · jdogresorg/freewallet-desktop
Desktop wallet for Win/Mac/Linux which supports Bitcoin and Counterparty - freewallet-desktop/uri-schemes.html at master · jdogresorg/freewallet-desktop
-
Does freewallet accept json ? as part of a unsigned tx .. I am finding I need to include Json data with scriptPubkeys when calling bitcoin-cli siggnrawtrransactionwithkey
-
No, no json, just the unsigned tx hash…. I believe bitcore and/or bitcoinjs should be able to sign the txs without json
-
interesting thanks!
I just need to work out how to deal with uncompressed public keys like the one your vanity address uses and my python dust searching script will be done -
counterparty-mpma-send-tool/index.html at be9a25c77cfe4570602f63d97f93d13991afa63b · jdogresorg/counterparty-mpma-send-tool
Counterparty Multi-Peer-Multi-Asset (MPMA) Send tool - counterparty-mpma-send-tool/index.html at be9a25c77cfe4570602f63d97f93d13991afa63b · jdogresorg/counterparty-mpma-send-tool
-
This may help with signing via JavaScript 😀👍🏻
-
thanks again
-
-
I think I have cracked it the address 1JDog... has 835 transactions and has created '7800 satoshi multisig dust' 17 times with a total of 39 unspent outputs totalling 304200 satoshi
-
nice!
-
ive got a lot of old addresses i used for testing when i built my xcp library back in 2015 so excited to use your tool lol
-
i originally built it using the op_checkmultisig method because at the time op_return availability was up in the air
-
Nice work…. One suggestion would be to allow ppl to adjust their dust level…. Most dust outputs are 7800…. But we have some that are 5430 and soon even lower at 546 sats…. Allowing ppl to set their desires dust level and searching for outputs with at least that much btc is prolly a good path forward.
-
I believe the old tool allows u to specify dust amount if I recall correctly
-
I hear you .. Unless I am mistaken 5430 sat outputs are not in bare multisig and are just regular utxos that are easy to sweep with electrum
-
but would be nice to include them and the 10,860 sat type stuff of old if I can get my head around it
-
I pip installed blockcypher and it busted my peter Todd python bitcoinnlib .. so annoying ..
I am now using 'requests' with http to bitcoin node rpc ..the less dependencies the better I
I can add code for the 5430/546 p2pkh outputs easily enough but the old 10860 stuff is a bit more challenging -
Got ya👍🏻
- 15 July 2022 (8 messages)
-
So bitcoincore reports that a 10860 dust output as being type ='non standard' and not as type='multisig' as it does for a 7800 dust ... Will be interesting to see if the 10860 non standard outputs are still spendable
-
How many txs have the 10860 outputs?
-
I don't know as my petertodd python bitcoinlib module doesn't work anymore so I am unable to trawl the blockchain with it to count
10860 outputs have not been used by counterparty for a while now -
I read through this and the rules on dust and it seems inconsistent within the code ...
counterpartylib config.py says multisig dust is = 7800 .. whereas counterblock config.py says its = 10860 (5430*2)
counterwallet seems to agree with counterpartylib (7800) .. so my guess is counterblock code outdated but unconsequential when it comes to creating dust as counterblock doesn't create transactions ? -
yeah thats probly accurate
-
correct, counterblock doesn't create transactions, the CP API does that... counterblock does proxy some requests to the CP API, but the actual transaction creation portion of things comes direct from the CP API.
-
Thanks .. my script is searching for 10860 dust in 1 of 2 nonstandard tx .. I tested it on the addresses that made TEST and CRYPTO .. One was done with a compressed public key the other an uncompressed key
- 22 July 2022 (14 messages)
-
Yep. Fucked. I rebuilt and everything.
-
Hi, your issuance was parsed without problems by counterparty servers. Please, update your node by doing:
> fednode update counterparty counterparty-testnet
and then
> fednode rebuild counterparty counterparty-testnet -
We pushed out an issuance update today to the CP servers…. Will get wrapped into the next release…. In the meantime run the above commands as Javier suggested n ur fednode n counterparty-lib will be updated with the issuance changes
-
FYI.. updating the API servers and xchain servers now with a fix for the "asterisk is being inserted into my description" issue.... finally tracked the issue down to an encoding flaw in Counterparty-lib... once this update is out on all the servers, the mysterious asterisk appearing in asset descriptions should be a thing of the past
-
Fixed token descriptions starting with an asterisk after putting a 42 characters long description by pataegrillo · Pull Request #1180 · CounterpartyXCP/counterparty-lib
Counterparty Protocol Reference Implementation. Contribute to CounterpartyXCP/counterparty-lib development by creating an account on GitHub.
-
-
I'm just running counterparty-server standalone without fednode. I need to re-bootstrap after getting the update, correct? -
the bootstrap hasn't been updated in a few weeks, so just update counterparty-lib codebase and restart it... your current database should be fine for now
-
when we push out the next release in another couple weeks, we will have the bootstrap updated, and just tell ppl to update and then run a cmd to remove their CP DB, so they pull down an updated version of the bootstrap with all the issuances normalized... but for now, you should be fine... only difference between your DB and the CP DB would be a couple different asset descriptions missing a single character at the beginning of the description (cuz we did away with pascal strings)
-
fucking pascal strings
-
- 26 July 2022 (12 messages)
-
just had a user use the Buy Now on a disp and it sent in 1 digit less I think and they did not get filled. Is this a bug than can happen? I was not able to recreate. -
Blockstream Block Explorer
Blockstream Explorer is an open source block explorer providing detailed blockchain data across Bitcoin, Testnet, and Liquid. Supports Tor and tracking-free.
-
disp
-
-
-
cannot think of another reason for the failure
-
What wallet did you send from?
-
Dispenser "Buy Now" sent 1 satoshi less than specified when buying one unit of give amount · Issue #77 · jdogresorg/freewallet-desktop
I used the "Buy now" button to buy 1 xcp from a dispenser, with give amount 1 xcp, for 0.00029999 BTC. Somehow there was sent 0.00029998 BTC and since it was 1 satoshi too little ...
-
Yeah… I gotta add some code that verifies that the send amount is at least the minimum amount to trigger the dispenser
-
Will try to tackle that while I’m in freewallet updating it to support oracled dispensers (pricing in fiat currencies)
-
Ok thks guys for the quick response
- 29 July 2022 (1 messages)
-
GitHub - loon3/counterparty-hw: Counterparty wallet for use with Ledger Nano S / S Plus / X
Counterparty wallet for use with Ledger Nano S / S Plus / X - GitHub - loon3/counterparty-hw: Counterparty wallet for use with Ledger Nano S / S Plus / X
- 31 July 2022 (11 messages)
-
lol
-
hodl mode
-
minting from ledger would be really cool
-
whats also cool is ledger live will automagically find addresses in your derivation path that hold corn, so managing dispensers should be fairly straightforward to integrate too
-
eventually, got a lot of ideas swimming around in my head now that i’ve got the most basic parts working
