Topic: [ANN][COMB] Haircomb - Quantum proof, anonymity and more - page 16. (Read 7225 times)

They could just be sending it yeah that's a good point, I thought something along those lines too but more to do with the fork that happened at the start but that could be unrelated. The only thing is.. the wallets sending the 546 txs have huge amounts of Btc in. That would be f*cking crazy for such an unknown project.
I've been claiming over the past few days but can't check how many yet, maybe one day I'll check and discover it's worth something haha

actually the bc1 tx is only for mining burn tip, meaning only when attempting to claim. but in the wallet when you want to send the comb somewhere, (and im assuming liquidity stacks as well) the tx's it asks you to send the 546 sats to fund for transfers ARE NOT BC1 addresses.
so its VERY probable that it has something to do with comb, it would make no other sense for SOOO many 546sat txs surrounding one specific address. or even generally 546sat specifically.

i agree on the idea that exchange has nothing to lose by adding this, and most likely would have such ideas since they are at the advantage for claiming.

what im curious about is if we can see when was the FIRST real claim of comb, can we trace it to AFTER the release of the wallet? if so then its fair game. but if by anychance there was ACTUAL comb claims BEFORE the release, then that would make the project lose credibility.

another interesting point is how under the table this whole project is at the moment. seems like there is not much reason to really go out and make it public, as that would DRAMATICALLY increase the competition. it would be way more advantageous to keep this more under the radar for the time being, to accumulate more while less competition and higher rewards.

trulying hoping that the release of the wallet was the first known claims and everything is honest. in that case, im predicting a quiet under the radar accumulation time, and then possibly more attention as more development is created.

ofcourse nobody knows and it could be nothing happens at all.

non the less there is potential for something great here (aslong as the release was completely honest and NO claims before the wallet release/ann thread)

if anyone has any ideas on how to help the project in the future, we can put our minds together and help out if needs be. though for now it seems to accumulate for cheap while we can is a better strategy, because if this actually adopts it will be VERY competitive and can easily be too expensive for any regular user to even attempt claiming.

when miners start to claim, it will be impossible for anyone other then the miners to claim. at that point the ONLY way you can get comb is buying from miners or previous other comb holders.

for now, anyone that is willing to spend 1-2$ can easily attempt and even successfully claim several times a day.

its most easy to claim when blocks are being found faster, as hashrate increases and difficulty poses to go up, blocks are being found faster, and not as many bc1 new outputs are even sent to the network, making cheap claims very possibly.

some of my cheapest claims are as low as 25sat/byte with total of under 6ksats for the total tx.

edit:grammer and proof read checks

I saw that but it's not to a bc1 address though? and a lot of exchanges send those small txs anyway to consolidate dust wallets. Binance did that a few days ago which is why the mempool spiked as it did, but yeah it was strange timing.
I think that's what the dev meant by it's only a matter of them sending to the Comb lottery first (in future), if Comb becomes popular then they have nothing to lose by doing so and if the coin is valuable then they stand to gain by claiming the block reward, as well as it creating a market for fees and everything else. It would make sense if the developer was a miner or affiliated with them or something, I personally don't believe it's just one person and a random 'interesting' project. Whoever released that whitepaper isn't just some random, in my opinion. But we will probably never know

I'd like to see this too. I looked into it and tried using Desmos but didn't work, and I think the floor part is Javascript "Math.floor()" function but I'm not a programmer, could be totally wrong

"MAX(2.1-FLOOR((LOG(h)/LOG(2))^6)/100000000, 0)
max is 12423823.18141419
and h is block number can start at current block"

noticed there has been a bunch of 546 sat txs surrounding this address lately 1HckjUpRGcrrRAtFaaCAUaGjsPx9oYmLaZ

any idea if it has anything to do with comb? what other reason would there be for specifically so many 546 sat tx's

looks like the 90mb bomb from a few days ago also had something to do with 546 sat tx's (if not mistaken)

That's interesting, sounds like you've really thought of everything. Where can I see liquidity stacks explained? But how will you give the coin history to everyone without essentially defeating the purpose of the privacy coin?

You (and others) might be thinking that I've completely lost my mind but let me reassure you that I am not crazy.

Yes, you're missing liquidity stacks. They are completely unusual feature in a crypto currency. Complete breakthrough.

In several years it's going to be completely normal to pay to 1000, 10000, or even 1 000 000 people using one payment, but currently that is not normal, it is not possible with almost all crypto currencies and this is why people do not think it's even possible.

But let me repeat again, it is actually possible.


Proof:

Suppose you want to pay 1000 people and you have their addresses.

You create a liquidity stack with 1000 entries, each entry specifies the next entry, the person's address, and the amount you pay to each of the people.

You end up with the first persons liquidity stack address.


Next you create a normal haircomb transaction from your address to the liquidity stack. NOT to the person. But to the liquidity stack!!!


This gives you 21 bc1q addresses that you need to fund on the bitcoin network.

Once these 21 addresses are funded on bitcoin blockchain (this is a small transaction) the 1000 people have been paid.


Only thing that remains is to give the transaction history to the 1000 people (the same to every person). But remember this does not happen on the blockchain, so it does not matter how large this history is.

Large history size is not a problem and there is no limit how huge the history can become.


When the receivers validate their coins they really own them.

even if you had 6billion addresses one for each person alive.
thats 6billion tx's that you need the btc network to do for you.
with 7 tx per second on avg, thats 604k tx per day, thats over 9k days, and over 27 years.
thats if you were the only one making txs on btc.

even if you give that double by making your tx's smaller somehow, thats still over 13years of blocks.
lets say you can even make your txs smaller then that by half, thats still over 6 years of blocks.


so even if you can make btc network produce 28tx's per second, and you had nobody else competing with you for block space. that would still take 6yrs of blocks.
this would cost an enormous amount in fees alone. aside from it not being practical in anyway.
unless theres something im completely missing.

so maybe its better to think of more realistic goals.

how does this even cross your mind?

makes me look at the whole project differently...

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.

You mean for a faucet or something?

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?

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!

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:

• 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.

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.

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.

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?

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 

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).