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

https://blockchair.com/bitcoin/mempool/transactions?s=fee_per_kwu(desc)&q=has_witness(true)#
this will help sort current fees in mempool
enjoy

All never seen p2wsh outputs of tx have the potential to claim comb. Not only the first output of tx.

But output 0 is considered first, then output 1 and so on.. in the output order.

if there is a multi output tx, and one of the outputs is a never seen p2wsh, but its not the first output of the tx.
would that count to be a possible claim?
or only if its the first tx in the multi output?

thanks

comb can be paid to haircomb addresses only. it cannot be paid to Bitcoin addresses such as 1xxxx 3xxxx or bc1xxxx.
The reason is the cryptography is very different.

Haircomb address consists of 64 numbers or letters A-F. It can be found in wallet, left to the COMB amount. (after you generate keys)

Another place to get an address is to use the haircomb paper wallet generator, this gives you both comb address and claiming address for one attempt in Bitcoin claiming (to that COMB address).

The user should keep the private key safe, in order to spend the funds from that address.
Private key looks like this /wallet/data/ followed by many characters.



There are two ways to export they shall never be confused. If you confuse them the receiver will steal your money that you give him by accident.

First is fully save as: File name: from the main page. This saves the full wallet including everything and secret keys too. The resulting file appears next to combfullui.exe and you should never give that file to anyone.

Second is export coin history only. This saves things but without the private keys. The coins will be deanonymized to the receiver. They will able to see those coins. But they will not be able to steal coins unless they own the private key.


There is only one import feature on the main page. It's universal. If the user sends you the coin history place it to a file. Then import that file.

You import your own wallets.dat using the same import feature.

Hope that helps

can you send comb to any btc address? or must it be an address generated from the comb client?
also once you send it and give the proof to someone, how do the receive and import it into comb client?
thanks!

Multi payment guide

Import the coin to your wallet:



Generate another key in your wallet. This will be your change address.
Click pay next to coin. Change address selection will appear:



Click the multipay option with your correct change address.



You can now add the destinations. The amount entered is in the smallest unit (1 unit = 0.00000001 COMB)



There can be arbitrarily many receivers limited only by the amount of RAM memory in your computer. The bitcoin fee paid is the same. If you have really powerful server and 77 COMB you can pay to 7 billion people.

Click do payment. Follow the instructions on the next screen. In particular save your wallet (from the main page) during this step.



We funded the 21addresses, and it confirmed. The payment is done.

Once it has 6 confirmations (not earlier!) you can go to main page, and export the coin history to file (right click , save as).

Post that coin history file to all the receivers.

New version of haircomb core 0.1.0 is available.

46f26569feb991e055cd817b2f1177a517151464a2661ea4e09e6a274fb8940a  combfullui
240416ed1bbb82be0fe8de2481a00fa1cf5e6c3b360e93f85edf479c1e2143fb  combfullui.exe

What is new

Bug fix - Importing large wallet infinite loop.
Feature - Multipayments to large amount of people - easy to use user interface available.

Who must upgrade

Only users who need the fix or want to use multi payments must upgrade. The rest of users can stay on old version.

Compatibility

No hard fork, no soft fork
No change of commits.db format
No change of modified bitcoin-qt api (you can keep using the old modified bitcoin core that you already have)

Upgrading

1. Shutdown bitcoin-qt
2. Shutdown haircomb core (of course save your wallet like on every shutdown)
3. Create a new folder for the new version and move there your commits.db
4. Start haircomb core
5. Start bitcoin-qt

Downgrading

The same except in step 3 you start using the old version of combfullui

How to do multiplayments

Guide will be posted shortly. Don't try it until then.

interesting, it looks like the reward decrease is very minimal and happens over VERY long period of time.
less then 7k new maximum amount of new comb per month on average
less then 82k new maximum amount of new comb per year
so in 5 years from now, we would have a maximum of less then 500k combs.

now considering almost more then 50% of blocks arent even claiming, (at the moment)
most likely less then 100 combs are being claimed per day.
the scarcity on comb is real.

Block 601002 is the haircomb genesis... It's the block in whitepaper. This means that noone could have succesfully claimed before that block and all coins before the launch are thus provably burned.

No premine. I've started claiming just as everyone else only after the whitepaper+wallet was posted.

I've subtracted f(601002)  = from the previous formula to make it start from zero coins at block 601002



I've zoomed in to the next 100 years period. Haircomb will operate over the course of 500 years.

which block # is genesis?

also can you help graph the reward amount?

how much comb will be reward at block 650k, 700k, 750k, ect.

Thank you

We can approximate the theoretical maximal number of COMB in circulation using an
Euler mcLaurin formula. Initial assumption is that every block since genesis
is claimed.

Remember the number of smallest units issued in given block is:

MAX(210000000-FLOOR((LOG(h)/LOG(2))^6), 0)

We ignore the MAX and limit ourselves to block heights h from 1 to 21835313

Clearly the supply f(n) at height n is the sum of the above formula from 1 to n:

f(n) = SUM h = 1 -> n  { 210000000-FLOOR((LOG(h)/LOG(2))^6) }

We ignore the FLOOR because we are doing only an approximation.
The 210000000 constant can be put out with multiplier n:

f(n) = 210000000*n - SUM h = 1 -> n  { (LOG(h)/LOG(2))^6 }

The approximation is thus the formula:

f(n) = 210000000*n - ((n*log(n)*log(n)*log(n)*log(n)*log(n)*log(n) - (720 *n *log(n)) + (720 *n) - (6 *n *log(n)*log(n)*log(n)*log(n)*log(n))  + (30 *n *log(n)*log(n)*log(n)*log(n))  -(120 *n* log(n)*log(n)*log(n))  + (360 *n *log(n)*log(n)))*9 - 6492 + log(n)*log(n)*log(n)*log(n)*log(n)*log(n)*4.5)

This is the excel formula (enter it into cell B1):

= 210000000*A1 - ((A1*LN(A1)*LN(A1)*LN(A1)*LN(A1)*LN(A1)*LN(A1) - (720 *A1 *LN(A1)) + (720 *A1) - (6 *A1 *LN(A1)*LN(A1)*LN(A1)*LN(A1)*LN(A1))  + (30 *A1 *LN(A1)*LN(A1)*LN(A1)*LN(A1))  -(120 *A1* LN(A1)*LN(A1)*LN(A1))  + (360 *A1 *LN(A1)*LN(A1)))*9 - 6492 + LN(A1)*LN(A1)*LN(A1)*LN(A1)*LN(A1)*LN(A1)*4.5)


Picture:

after you attempted a claim and its included in a block. take a look at that block and look from the top down, look for the first bc1 address output (also needs to be p2wsh, sometimes its P2WPKH, if im not mistaken those wont count), see if its new. if not keep going. until you see yours. if yours is the first new bc1 (p2wsh) then you most likely won.

at least in my experience that is how it worked so far. and you can change your sat/byte accordingly.

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