You mean for a faucet or something?
Yeah I'm thinking about paying 0.00000001 COMB to every single person alive. It's possible with today's tech. Only problem is getting the massive list of addresses.
Topic: [ANN][COMB] Haircomb - Quantum proof, anonymity and more - page 16. (Read 6890 times)
Yeah I'm thinking about paying 0.00000001 COMB to every single person alive. It's possible with today's tech. Only problem is getting the massive list of addresses.
Hello. Recently I've been thinking a lot about this.
Suppose someone had 77.5 COMB what would that person do with them?
If you read this thread carefully then you probably know what I mean.
I know it would be really complicated and some people could pose like two people and so on.
But suppose the final list could be assembled. How would you deliver that list to the person and then back the transaction history?
Suppose someone had 77.5 COMB what would that person do with them?
If you read this thread carefully then you probably know what I mean.
I know it would be really complicated and some people could pose like two people and so on.
But suppose the final list could be assembled. How would you deliver that list to the person and then back the transaction history?
You mean for a faucet or something?
Hello. Recently I've been thinking a lot about this.
Suppose someone had 77.5 COMB what would that person do with them?
If you read this thread carefully then you probably know what I mean.
I know it would be really complicated and some people could pose like two people and so on.
But suppose the final list could be assembled. How would you deliver that list to the person and then back the transaction history?
Suppose someone had 77.5 COMB what would that person do with them?
If you read this thread carefully then you probably know what I mean.
I know it would be really complicated and some people could pose like two people and so on.
But suppose the final list could be assembled. How would you deliver that list to the person and then back the transaction history?
Re-read the whole thread.
Have no idea what your talking about.
Hello. Recently I've been thinking a lot about this.
Suppose someone had 77.5 COMB what would that person do with them?
If you read this thread carefully then you probably know what I mean.
I know it would be really complicated and some people could pose like two people and so on.
But suppose the final list could be assembled. How would you deliver that list to the person and then back the transaction history?
Suppose someone had 77.5 COMB what would that person do with them?
If you read this thread carefully then you probably know what I mean.
I know it would be really complicated and some people could pose like two people and so on.
But suppose the final list could be assembled. How would you deliver that list to the person and then back the transaction history?
having an issue now where the qt client says "done loading" and just stays like that. i did everything correctly as far as i know and shut down the proper way, but on startup. after verifying blocks, just says done loading and either freezes there or just closes after some time.
edit:
might of corrupted the commits.
ill try give it another new sync, and will test again.
could be error on my part somewhere
edit2: fully synced everything working
edit3: can anyone graph the supply over time on a chart? for example desmos?
would love to see how the supply goes over time. to see how much will the reward claim be at 50k blocks from now, 100k blocks, ect.
to see how the reward is effected over time.
thanks!
edit:
might of corrupted the commits.
ill try give it another new sync, and will test again.
could be error on my part somewhere
edit2: fully synced everything working
edit3: can anyone graph the supply over time on a chart? for example desmos?
would love to see how the supply goes over time. to see how much will the reward claim be at 50k blocks from now, 100k blocks, ect.
to see how the reward is effected over time.
thanks!
PRUNING
Pruning is supported. Set prune=1 in your bitcoin-qt and restart it. This will enable manual prune.
Next open core command line and enter:
pruneblockchain 481822
Then wait till a number appears. Once it appears about 100 GB of ancient blockchain data was deleted.
This is especially useful/crucial for SSD disk users.
Next, 3 advises.
1. The commits.db should be backed up when both the wallet and bitcoin-qt is correctly shutdown. Not while it is running.
2. If you need to restore backup commits.db, do it when both the wallet and bitcoin-qt is correctly shutdown. Not while it is running.
3. The Sending commitments screen exists because haircomb core upon startup detected that your commits.db is corrupt and it is recreating a new one. Possible reasons:
I also strongly advise everyone to manually fully save your wallet to a file as often as needed because the wallet has no auto save feature - it was easier to develop that wallet in this way.
I already dodged a bullet several times using this method.
it is you who is responsible for saving your own wallet to a files of your choice as often as needed but especially every time after creating new keys and new liquidity stacks.
Pruning is supported. Set prune=1 in your bitcoin-qt and restart it. This will enable manual prune.
Next open core command line and enter:
pruneblockchain 481822
Then wait till a number appears. Once it appears about 100 GB of ancient blockchain data was deleted.
This is especially useful/crucial for SSD disk users.
Next, 3 advises.
1. The commits.db should be backed up when both the wallet and bitcoin-qt is correctly shutdown. Not while it is running.
2. If you need to restore backup commits.db, do it when both the wallet and bitcoin-qt is correctly shutdown. Not while it is running.
3. The Sending commitments screen exists because haircomb core upon startup detected that your commits.db is corrupt and it is recreating a new one. Possible reasons:
- you shut down your pc while core was running - don't ever do this
- the wallet crashed due to problem that I caused - improbable - you will see error in the comb window and then it will close
- you shut down your core improperly - don't ever do this
I also strongly advise everyone to manually fully save your wallet to a file as often as needed because the wallet has no auto save feature - it was easier to develop that wallet in this way.
I already dodged a bullet several times using this method.
it is you who is responsible for saving your own wallet to a files of your choice as often as needed but especially every time after creating new keys and new liquidity stacks.
what for?
ill sync my client it should be done in a few hours, and i will be more careful to save the commits.db and shut it down properly.
how do you know those 3000 are successful? if you dont have a fully synced node?
wow thats alot! what was your average price in fees did you use? sat/byte?
did you find any patterns or better times to claim?
any specific strategy you used?
how much sat per tx average per claim?
ill sync my client it should be done in a few hours, and i will be more careful to save the commits.db and shut it down properly.
how do you know those 3000 are successful? if you dont have a fully synced node?
wow thats alot! what was your average price in fees did you use? sat/byte?
did you find any patterns or better times to claim?
any specific strategy you used?
how much sat per tx average per claim?
No no I don't mean I claimed that many, I don't know how many I claimed (maybe even 0) because my wallet isn't synced. But the addresses were posted somewhere else and I saved them so I could see what fee they used when I was trying to claim. The wallet will take too long for me to sync (slow connection and computer) so I gave up with that for now. But maybe they will help you work out what kind of txs work best when claiming. I tried looking when I was claiming but I'm not technically proficient enough to know if any were odd etc.
Sure make a pastebin. Would love to take a look at successful claims to see more info.
Are these your 3k attempts? or where did you find this list.
what for?
ill sync my client it should be done in a few hours, and i will be more careful to save the commits.db and shut it down properly.
how do you know those 3000 are successful? if you dont have a fully synced node?
wow thats alot! what was your average price in fees did you use? sat/byte?
did you find any patterns or better times to claim?
any specific strategy you used?
how much sat per tx average per claim?
ill sync my client it should be done in a few hours, and i will be more careful to save the commits.db and shut it down properly.
how do you know those 3000 are successful? if you dont have a fully synced node?
wow thats alot! what was your average price in fees did you use? sat/byte?
did you find any patterns or better times to claim?
any specific strategy you used?
how much sat per tx average per claim?
No no I don't mean I claimed that many, I don't know how many I claimed (maybe even 0) because my wallet isn't synced. But the addresses were posted somewhere else and I saved them so I could see what fee they used when I was trying to claim. The wallet will take too long for me to sync (slow connection and computer) so I gave up with that for now. But maybe they will help you work out what kind of txs work best when claiming. I tried looking when I was claiming but I'm not technically proficient enough to know if any were odd etc.
only way i was able to check is from full sync. i had it going yesterday, but i guess the commits.db didnt save so resyncing it again today.
still not 100% sure how it exactly works, since ive noticed times when i used low sat/byte and i was really far down in the block, and had many other tx's to bc1 addresses that were also p2swh txs but i still got the claim. edit: meaning other txs payed higher fee and were ontop of mine and also to bc1 addresses and also p2swh but i still got the claim
so im wondering what explorer i can use to identify which exact type of tx will work for a claim, this way i can scout previous blocks and see whats going on to somehow predict the network activity that the next block might bring.
currently i used blockstream.info
I have a list of 3000 successful comb claims if you want I can email you it or something or post it in a pastebin
what for?
ill sync my client it should be done in a few hours, and i will be more careful to save the commits.db and shut it down properly.
how do you know those 3000 are successful? if you dont have a fully synced node?
wow thats alot! what was your average price in fees did you use? sat/byte?
did you find any patterns or better times to claim?
any specific strategy you used?
how much sat per tx average per claim?
only way i was able to check is from full sync. i had it going yesterday, but i guess the commits.db didnt save so resyncing it again today.
still not 100% sure how it exactly works, since ive noticed times when i used low sat/byte and i was really far down in the block, and had many other tx's to bc1 addresses that were also p2swh txs but i still got the claim. edit: meaning other txs payed higher fee and were ontop of mine and also to bc1 addresses and also p2swh but i still got the claim
so im wondering what explorer i can use to identify which exact type of tx will work for a claim, this way i can scout previous blocks and see whats going on to somehow predict the network activity that the next block might bring.
currently i used blockstream.info
I have a list of 3000 successful comb claims if you want I can email you it or something or post it in a pastebin
Is there a way to check if you have successfully claimed or not without the wallet being synced? The Comb Rewards Viewer site seems to be broken (unless it requires the wallet to be synced).
only way i was able to check is from full sync. i had it going yesterday, but i guess the commits.db didnt save so resyncing it again today.
still not 100% sure how it exactly works, since ive noticed times when i used low sat/byte and i was really far down in the block, and had many other tx's to bc1 addresses that were also p2swh txs but i still got the claim. edit: meaning other txs payed higher fee and were ontop of mine and also to bc1 addresses and also p2swh but i still got the claim
so im wondering what explorer i can use to identify which exact type of tx will work for a claim, this way i can scout previous blocks and see whats going on to somehow predict the network activity that the next block might bring.
currently i used blockstream.info
Is there a way to check if you have successfully claimed or not without the wallet being synced? The Comb Rewards Viewer site seems to be broken (unless it requires the wallet to be synced).
ive noticed when shutting down the wallet, then turning it back on, it takes a long time "sending commitments press q to shutdown x%"
is this normal? does this always take a long time when restarting the client? is there anything that can be done to speed that up? i mean after having a fully synced node, and restarting same thing takes forever to load back up
edit:
looks like forgot about this step
"general usage - shutdown
1. close bitcoin core, wait until the close window disappears.
2. go to 127.0.0.1:2121 and press safe shutdown. The wallet should close.
general usage - startup
1. start combfullui.exe
2. go to 127.0.0.1:2121, verify it is running
3. start bitcoin-qt.exe
general usage - commits.db database backup
1. shutdown bitcoin core, then safe shutdown combfullui.exe
2. copy commits.db to a backup location while the wallets are shutdown."
will make sure to copy the commits.db this time, and shut down properly.
is this normal? does this always take a long time when restarting the client? is there anything that can be done to speed that up? i mean after having a fully synced node, and restarting same thing takes forever to load back up
edit:
looks like forgot about this step
"general usage - shutdown
1. close bitcoin core, wait until the close window disappears.
2. go to 127.0.0.1:2121 and press safe shutdown. The wallet should close.
general usage - startup
1. start combfullui.exe
2. go to 127.0.0.1:2121, verify it is running
3. start bitcoin-qt.exe
general usage - commits.db database backup
1. shutdown bitcoin core, then safe shutdown combfullui.exe
2. copy commits.db to a backup location while the wallets are shutdown."
will make sure to copy the commits.db this time, and shut down properly.
looks like from natasha previous answer that yes to send comb from one address to another 21 burnt addresses need to be funded,
though it seems it doesnt have to be a single tx, and instead can be a multiple output tx, so funding 21 burnt addresses can be sending and receiving of multiple addresses,
yes we are early,
though it seems it doesnt have to be a single tx, and instead can be a multiple output tx, so funding 21 burnt addresses can be sending and receiving of multiple addresses,
yes we are early,
what do you think is a fair price? how bout 50k sats
edit2: what happens to a failed attempt? i see the mining address is not shown in the wallet anymore, can i still use the same mining address to try again?
or only can use a new one?
You can't use the same mining address twice even if the first claim was unsuccessful. I wasted some btc attempting it (sent about 40txs, lol). And if someone else (a non Comb address) claims the Comb from the block then that Comb is burned since they can't access it. I think the best way to claim is by checking the mempool for the highest fee and then paying more than it, so if you know of any good sites to check for that then I'm interested to hear it.
Did you find out if when sending 1 Comb you have to send 546 sats to 21 addresses by the way? Pretty interesting if so because every time Comb is sent then BTC would be burnt simultaneously. I haven't tried to send any yet.
im looking to buy some comb, if anyone would be nice to sell some let me know, we can use an escrow if needed,
5k-10k sats per comb depending on amount, can also neg a better rate depending on quantity
5k-10k sats per comb depending on amount, can also neg a better rate depending on quantity
Pretty sure it costs more than that in fees to claim.
what do you think is a fair price? how bout 50k sats
edit: come to think of it, small transfers wouldnt be worth atm since alot of it would be to fees.
might have to just continue my luck on claiming instead.
edit2: what happens to a failed attempt? i see the mining address is not shown in the wallet anymore, can i still use the same mining address to try again?
or only can use a new one?
im looking to buy some comb, if anyone would be nice to sell some let me know, we can use an escrow if needed,
5k-10k sats per comb depending on amount, can also neg a better rate depending on quantity
5k-10k sats per comb depending on amount, can also neg a better rate depending on quantity
Pretty sure it costs more than that in fees to claim.
im looking to buy some comb, if anyone would be nice to sell some let me know, we can use an escrow if needed,
5k-10k sats per comb depending on amount, can also neg a better rate depending on quantity
5k-10k sats per comb depending on amount, can also neg a better rate depending on quantity
im curious on how the supply mechanics of this comb token works, does the amount per claim change?
Don't know the mechanics of how or why it changes but the amount per claim seems to change slightly.
1.59906193 COMB
1.59906156 COMB
1.59906118 COMB
The last 4 digits at least. If you mean over time like halvening then I'm not sure
Edit: Read the whitepaper again.
"The supply has 8 decimal places, reward decreases at a subexponential rate. System scales with the number of inputs spent multiplied by the size of one signature (21 hashes). Using a Merkle tree segment signer can route coin to one of 65536 outputs by revealing two commitments (2 hashes), enabling atomic swaps and other constructs."
the implications on if this actually takes off, this can be really huge for bitcoin.
one is that it will be a further btc sink, as if the 546 sat txs are actually verifiably burnt, then thats great for overall deflation of btc!
2nd is that, this can create a more competitive tx fee market, even if just for 1 claim per block, it can put a staple for atleast 1 tx pet block to have a higher fee, overall this helps support the security of the btc network since it helps create market for layer one fees.
im curious to see more prominent btc devs say on this project. as this could be a potentially huge advancement, having totally anonymous transfer on btc first layer, and creating further deflation, and ontop of that helping create a higher fee market, its a win win in every direction for btc. (atleast in my opinion)
if this takes off, we might even see different flavors of such tokens on the network, further increasing deflation, and also further creating more market for fees.
higher fees is essential imo for btc security long term.
im curious on how the supply mechanics of this comb token works, does the amount per claim change?
one is that it will be a further btc sink, as if the 546 sat txs are actually verifiably burnt, then thats great for overall deflation of btc!
2nd is that, this can create a more competitive tx fee market, even if just for 1 claim per block, it can put a staple for atleast 1 tx pet block to have a higher fee, overall this helps support the security of the btc network since it helps create market for layer one fees.
im curious to see more prominent btc devs say on this project. as this could be a potentially huge advancement, having totally anonymous transfer on btc first layer, and creating further deflation, and ontop of that helping create a higher fee market, its a win win in every direction for btc. (atleast in my opinion)
if this takes off, we might even see different flavors of such tokens on the network, further increasing deflation, and also further creating more market for fees.
higher fees is essential imo for btc security long term.
im curious on how the supply mechanics of this comb token works, does the amount per claim change?
Jump to: