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

how much comb to be considered a major holder?

no objection here.

upgraded and good to go.

thanks!

New version of haircomb core 0.2.0 is available.

4d9adaeb67238a9482fbfc4ce0ba8beb5f10233acea4727ad7c5da877e99bca5  combfullui
c783d53115e3c304ba09bef6b90fb4db40c37b0ffd90877149679382a4071568  combfullui.exe

What is new

Fork - liquidity stack output coin can loop back to the same liquidity stack safely

Who must upgrade

All users must upgrade. There is no observable change noticeable by end user
compared to the old 0.1.0 version, except for the underlying fork.

Compatibility

This is a 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

I'm ready. Are you boys ready?  Fork tomorrow or Saturday.

Any objections from major holders?

Please let everyone know.

Hello boys, this is an update. Next version seems doable (sometimes next year).

It will be a fork, version number will be 0.2.0.

It will make it possible to create liquidity stack coin loops. Briefly liquidity stack coin loop is when you pay using liquidity stack to an address that will eventually redirect the coin to the same liquidity stack. Under the current rules such coins will be destroyed.

I propose a new rule that will instead send the coin to the change address. This will enable entities to pay back to themselves using stealth address safely. Or to their own old addresses. The coins will simply fall down to their own change addresses and won't be destroyed.

After the fork we will most certainly see a flood of new features most importantly:

stealth addresses - basically you will have your main haircomb address with all your funds on it and have the ability to create any number of stealth addresses to receive coins to this your main address. Funds from others sent to the stealth address redirect to your backing address without fees and without revealing the backing address to anyone.

Stealth addresses are basically feeless redirect addresses.

safe operation of exchanges or custodians - using stealth addresses basically allows custodians or exchanges to operate safely. They generate new stealth address for every deposit for every customer. This fork (0.2.0) brings the new feature that when two customers on the same exchange pay to each other the coins won't be destroyed (due to loop) but simply fall back down to the exchange hot wallet as they should. This is why this fork is so important.

i took at look at txstreet.com but i cant see where i can see ONLY the highest with a p2wsh output, or even just to check the highest bc1 like you said. but theres nowhere to tick and see the txs in an organized form. unless im missing something. or if your talking about reading their data and organizing it yourself

Hello boys. The project is alive. I'm working on the liquidity stack loops. It will be done when the numbers tell me it's done and not earlier.

I'm working on it in my spare time and I am not paid but that is not the problem. Money won't accelerate the progress only brain power will. I feel that my coins going up in value eventually will be the best reward.

Yeah you have to outbid highest fee payer.

About the possibility of haircomb on BSV or on BCH, it's not directly possible since there is no segwit and thus no 256bit addresses that I am aware of.

Even if those coins had 256bit addresses it would be a not so great idea to run haircomb on it. The reason is it uses sha256 hashing and is prone to 51%/reorg attacks. And succesfull 51 % attack means recently-transacted coin destruction in the worst case (if the attacking miner knows the haircomb coins history)

Haircomb on Litecoin would be a possibility though, it's reasonably powerful, has segwit, and not prone to 51% attacks.

couldn't I just go to:
https://txstreet.com/

from there View the live block, which right now is
https://www.blockchain.com/btc/block/0000000000000000000194594e2a29761b26bb9261dba2c17fe24467fe161a71

and then just find the highest bc1?

so right now the highest bc1 fee is 0.00040000 ($2.829)

So I'd have to outbid them to claim comb?

--

&
would it be difficult to make haircomb for BSV or even bch?

any news on whats going on?
anything you working on?
would it be a good idea to be more public about this project so its not looked like it was premine in the early days

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.