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

What would you consider to be a fair price for comb at current state? how many sats do you think are spent in average before one gets a successful claim?

any chance somebody can help by creating a tool to monitor mempool live, and show highest fee unseen p2wsh. this way to help claiming. would help manual claiming tremendously. i assume eventually there will be bots automating this.

Neither but if someone looking to buy, i can arrange something and use the funds to further claim.
Ofcourse taking a fee because future claims aren't guaranteed.

has anyone sold/bought any haircomb yet? or are currently trying to sell them?

There is not and won't be any way to pay from multiple keys at once.

Our combs are on different keys too. We combine the comb by paying to another
address with comb on it when the mempool is empty and fees are cheap.

Or just wait until you need to pay to more people to make it worth the bitcoin
fee. For example you can sell the comb to different people for pennies.

You can as well claim more comb using the combining payment, simply use a claim
adress as the first address following by 21 commitments, in total 22 addresses.

fold stack - don't use this. it's an experimental feature that merges addresses
you entered so far into one liquidity stack address with their total amount.
It's only used when paying to millions of people or more.

do payment - it's used to continue with the payment when you are ready


New version of haircomb core 0.2.2 is available.

b8b6bb972119b07c570989314617af81a2329c5cd08770ac8404815675190198  combfullui
c9f50a3ed90190e0d33e64342178d2f8cbc70d9e7e64f4736ad6e9a7ad025454  combfullui.exe


What is new

Block reorganization bug fixes - 3 bug fixes - on reorg mine only combbases not all commits, remove combbase from combbases on reorg, set graph dirty on reorg
Loop detector bug fix - this is a safety feature that was fixed to avoid paying to loops
Liquidity stack trickle bug - fixes hang when someone paid to liquidity stack that has 0 amount that caused a loop

Who must upgrade

All users are highly recommended to upgrade because there are reorg fixes

Compatibility

Not 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

whats the best way to combine claims from separate generated addresses to a new main address?
now that we have stealth addresses attached to one address.
is there a good way i can combine previous claims to one address?
do i need to fund 21 addresses for each previous claim i would like to move?

or is there a way to make a liquidity stack with all previous claims to go into 1 address
by only funding 21 addresses one time?

the liquidity stacks and funding is a bit confusing still.
what does fold stack do? what does to payment do?

mainly would like to know if i want to send comb from several addresses, does each one need to fund 21 addresses or can liquidity stacks work for inputs as well as outputs?

Only a heads up

Next version will be 0.2.2, It will contain a fixes for two medium severity issues.

One big area I want to focus on next is history minimization. It's a feature that allows you to only send history related to a specific coin to the person you are paying to.

History minimization anonymizes all unrelated coins.

I want to have basic history minimization in 0.2.2

As well as I want to work on jsonrpc console, that will be needed for an exchange integration

If you read through the thread there is information on this already.

But in short you generate an address through the wallet. And send 546 satoshi with a fee that will give you a chance of being the first unseen p2wsh in the block.
If you are the first p2wsh unseen in the block, you have successfully claimed the comb.

With the addition of stealth addresses you can just claim to each new stealth address and then sweep it to your main address.

Ok so how do i claim/buy/mine comb right now?,
i know you can't mine it,
and theoretically also not buy it,
but i'd really like to know how to get hold of comb right now,
i have btc (so sats) and i'd be ready to tip them but i don't know to where, i'm currently syncing my wallet (250gb download), can someone explain to me how to get comb?

The step by step guide was made for multi-payments. It works.

Main risks when transacting

Scammer trying to help you

  Never send your fully saved wallet to anyone. I will never ask you for your
  wallet, I will request only the transaction history.

Loss of funds due to paying to something that appears
to be an address but it is not an address - or mistyping an address or amount.

  This risk can be eliminated by never typing addresses manually. Pay attention
  to the amounts. Always enter amount in smallest unit (1 unit =0.00000001 COMB),
  never use decimal or thousands separators or spaces. Make sure you are not tired or
  under stress when entering the payment. Double check the total amount displayed.

Funds stuck due to overpaying

  Overpaying means when someone pays 10 COMB while only having 4 COMB in the key.
  What will happen the 4 COMB will be stuck pending for additional 6 COMB paid
  to the same liquidity stack. Never attempt to resolve the situation yourself
  by sending the missing amount. Always stop, fully save your wallet immediately
  once more (to be sure) and ask for assistance if this happens to you.
  If you overpay by a huge amount - for example you pay 9000000.00000000 COMB to
  someone, the funds are most likely effectively lost, but it depends how you
  paid and in what order in the transaction.

Loss of funds due to a confirmed doublespend - due to changing your
mind about the destinations while a transaction was ongoing.

  Unlike in Bitcoin, you cannot change your mind if the 21 addresses
  do not confirm on the blockchain. You need to retry paying again later to
  the same 21 addresses with higher fee. If you modify the transaction you get
  different 21 addresses, never show these to anyone and never pay to them.
  The point of no return is revealing the first 21 addresses made from a key
  to the public.


If you avoid these risks you will be fine

is there a simple step procedure of sending comb from one user to another?
what would be the best way to go about sending comb?
thanks

Now hehe

New version of haircomb core 0.2.1 is available.

4be2076a5aac1b7672c1c545deed1e440e1db6c86ec8790b20bdbd3b37f8fc14  combfullui
bc6c59db6be63fd53dce5508b27b7be108d4c51b72d8bd8a1c558a421313d7ff  combfullui.exe

What is new

Stealth addresses - each wallet address has plenty of stealth addresses. You can
claim using them as well as receive funds. Before that or after that you can
sweep the funds into your main address.

Safety feature - history export now requires a minimum of 6 (or 7 - to be
determined?) confirmations in order to export your transaction. This means
that you will not expose your commits by accident and won't give a malicious
counterparty a chance to destroy your funds.

Who must upgrade

If you want to try the new features you should update. Otherwise you can stay at
0.2.0. But remember, there is a new safety feature so you perhaps should update.

Compatibility

Not 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

when 0.2.1?

It is working this time, thanks!

make sure to follow proper steps on shutting down, at first i didnt notice them and corrupted the commits and needed to start over.

Hello! I have version 0.2.1 ready!

It has an awesome feature - stealth addresses.



Hello, there is a known limitation in the modified bitcoin core. When running completely for the first time, you should restart the bitcoin core after a while.

The reason is the code that activates the sending of the commits is coded in the intro window. And the intro window is not shown when you run exactly for the first time.

Or you can reset it when you fully sync, It's up to you. The point is seeing the intro window.

Hello there!

I just learned about this project and I am trying to sync the wallet.
I was past block 500k yet it wasn't synced up and commits.db file was empty.

I decided to restart the process just in case, it is approaching that block number again and the commits.db is still empty.

Should I still follow that procedure? (Besides getting the latest versions from the repo)

edit: will wait for 602614+ blocks as seen on post

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.