Topic: [ANN][COMB] Haircomb - Quantum proof, anonymity and more (Read 7091 times)
Combfullui 0.5.3 released. Users can upgrade if needed.
https://codeberg.org/watashi564/combfullui/releases
Combdownloader 0.1.8 released. Upgrade is optional.
https://codeberg.org/watashi564/combdownloader-ng/releases
Combapp 0.1.3 released. Upgrade is optional.
https://codeberg.org/watashi564/combapp/releases
Haircomb docker 0.1.3 released.
https://hub.docker.com/r/haircombs/haircomb
All known issues were resolved. Everyone is invited to visit the haircomb wiki at:
https://wiki.haircomber.com
Combfullui 0.5.2 released. Users can upgrade if needed.
Hard fork can be optionally activated by users who are willing to trade.
https://codeberg.org/watashi564/combfullui/releases
Combdownloader 0.1.7 released. Upgrade is optional.
https://codeberg.org/watashi564/combdownloader-ng/releases
Combapp 0.1.2 released. Upgrade is optional.
https://codeberg.org/watashi564/combapp/releases
Haircomb docker 0.1.2 released.
https://hub.docker.com/r/haircombs/haircomb
All known issues were resolved.
Attention
swap.haircomber.com - Sell: Step 5: Pay and send - Destination Amount (Natashas): Is currently in hexadecimal (base 16)
It is unknown whether this caused any fund loss - most likely outcome is that Seller pays the wrong amount, and Buyer rollbacks the deal.
Attention
- unknown bug/glitch in hardfork, funds may not getting displayed with hardfork = on
swap.haircomber.com - Sell: Step 5: Pay and send - Destination Amount (Natashas): Is currently in hexadecimal (base 16)
It is unknown whether this caused any fund loss - most likely outcome is that Seller pays the wrong amount, and Buyer rollbacks the deal.
Attention
- unknown bug/glitch in hardfork, funds may not getting displayed with hardfork = on
Today marks a big day for the evolution of haircomb.
The COMB / Ethereum trading pair is now live on https://swap.haircomber.com/
What this means:
- The hard fork is active on all my nodes. All people who trade should enable it too.
- Someone should verify that the contract works. This is done by trading 1 Nat for 1 Wei.
- After that people who know what they are doing can start initiating larger deals.
People should monitor relevant channels to see if there are any bugs/fixes.
If you don't know how to trade, practice on the testnet.
The COMB / Ethereum trading pair is now live on https://swap.haircomber.com/
What this means:
- The hard fork is active on all my nodes. All people who trade should enable it too.
- Someone should verify that the contract works. This is done by trading 1 Nat for 1 Wei.
- After that people who know what they are doing can start initiating larger deals.
People should monitor relevant channels to see if there are any bugs/fixes.
If you don't know how to trade, practice on the testnet.
Combfullui 0.5.1 released. Users can upgrade if needed.
https://codeberg.org/watashi564/combfullui/releases
Combdownloader 0.1.6 released. Upgrade is optional.
https://codeberg.org/watashi564/combdownloader-ng/releases
Combapp 0.1.1 released. Upgrade is optional.
https://codeberg.org/watashi564/combapp/releases
Haircomb docker 0.1.1 released.
https://hub.docker.com/r/haircombs/haircomb
https://codeberg.org/watashi564/combfullui/releases
Combdownloader 0.1.6 released. Upgrade is optional.
https://codeberg.org/watashi564/combdownloader-ng/releases
Combapp 0.1.1 released. Upgrade is optional.
https://codeberg.org/watashi564/combapp/releases
Haircomb docker 0.1.1 released.
https://hub.docker.com/r/haircombs/haircomb
Combfullui 0.5.0 released. Users can upgrade if needed.
https://codeberg.org/watashi564/combfullui-0.4.3-nodowntime/releases
Combdownloader 0.1.5 released. Upgrade is optional.
https://codeberg.org/watashi564/combdownloader-ng/releases
Combapp 0.1.0 released. Upgrade is optional.
https://codeberg.org/watashi564/combapp/releases
Haircomb docker 0.1.0 released.
https://hub.docker.com/r/haircombs/haircomb
https://codeberg.org/watashi564/combfullui-0.4.3-nodowntime/releases
Combdownloader 0.1.5 released. Upgrade is optional.
https://codeberg.org/watashi564/combdownloader-ng/releases
Combapp 0.1.0 released. Upgrade is optional.
https://codeberg.org/watashi564/combapp/releases
Haircomb docker 0.1.0 released.
https://hub.docker.com/r/haircombs/haircomb
Combfullui 0.4.3 released. Users can upgrade if needed.
https://codeberg.org/watashi564/combfullui-0.4.2-maintenance/releases
Combdownloader 0.1.4 released. Upgrade is optional.
https://codeberg.org/watashi564/combdownloader-ng/releases
Combapp 0.0.9 released. Upgrade is optional.
https://codeberg.org/watashi564/combapp/releases
Haircomb docker 0.0.9 released.
https://hub.docker.com/r/haircombs/haircomb
New website for haircomb introduction and claiming:
https://haircomber.com
https://codeberg.org/watashi564/combfullui-0.4.2-maintenance/releases
Combdownloader 0.1.4 released. Upgrade is optional.
https://codeberg.org/watashi564/combdownloader-ng/releases
Combapp 0.0.9 released. Upgrade is optional.
https://codeberg.org/watashi564/combapp/releases
Haircomb docker 0.0.9 released.
https://hub.docker.com/r/haircombs/haircomb
New website for haircomb introduction and claiming:
https://haircomber.com
Interesting concept! Of the privacy aspect read the whitepaper and gives me a quantum anonymous Mimble-Wimble powers
A balance/dynamic inflation on coin supply emission which is ok in my vision. Too much heavy inflation is no good in my opinion, though (IAM not always 100% accurate on crypto currency matters. And I'm no expert on side of blochain or coding. Iam moderate experienced in the basic know hows. Iam a basic end user. Liking to ease of use for digital money/bitcoin).
I have tried the honeycomb application "software" some days ago (I don't remember everything entirely) but what I do remember is that honeycomb script file in process of connecting with the bitcoin core Blockchain. I got excited at first but realised this is not a standalone honeycomb Blockchain system.
So yeah, it's okay, I don't have good understanding but the technology behind this is maybe good?
my hard-drive capacity is not enough to generate a bitcoin core address. i dont have bitcoins sofware it's out-dated. but my hadware is up-to-date for this current time
A balance/dynamic inflation on coin supply emission which is ok in my vision. Too much heavy inflation is no good in my opinion, though (IAM not always 100% accurate on crypto currency matters. And I'm no expert on side of blochain or coding. Iam moderate experienced in the basic know hows. Iam a basic end user. Liking to ease of use for digital money/bitcoin).
I have tried the honeycomb application "software" some days ago (I don't remember everything entirely) but what I do remember is that honeycomb script file in process of connecting with the bitcoin core Blockchain. I got excited at first but realised this is not a standalone honeycomb Blockchain system.
So yeah, it's okay, I don't have good understanding but the technology behind this is maybe good?
my hard-drive capacity is not enough to generate a bitcoin core address. i dont have bitcoins sofware it's out-dated. but my hadware is up-to-date for this current time
Attention, malicious video file in telegram comb_talk. 
thanks for the warning, i nearly lost all my bald coin
Attention, malicious video file in telegram comb_talk.
nice
is the advice for claiming in this thread still current or is there a new guide?
is the advice for claiming in this thread still current or is there a new guide?
Combfullui 0.4.2 released. Users can upgrade if needed.
https://codeberg.org/watashi564/combfullui-0.4.1-pricechart/releases
Combdownloader 0.1.3 released. Upgrade is optional.
https://codeberg.org/watashi564/combdownloader-ng/releases
Combapp 0.0.8 released. Upgrade is optional.
https://codeberg.org/watashi564/combapp/releases
Haircomb docker 0.0.8 released.
https://hub.docker.com/r/haircombs/haircomb
https://codeberg.org/watashi564/combfullui-0.4.1-pricechart/releases
Combdownloader 0.1.3 released. Upgrade is optional.
https://codeberg.org/watashi564/combdownloader-ng/releases
Combapp 0.0.8 released. Upgrade is optional.
https://codeberg.org/watashi564/combapp/releases
Haircomb docker 0.0.8 released.
https://hub.docker.com/r/haircombs/haircomb
hi, all
is this project still current? i'm looking for interesting ideas for quantum resistance and scaling on the bitcoin blockchain, haircomb is the only one that i remember but it seems pretty dead these days.
hope the project can be revived someday. is natasha still out there?
is this project still current? i'm looking for interesting ideas for quantum resistance and scaling on the bitcoin blockchain, haircomb is the only one that i remember but it seems pretty dead these days.
hope the project can be revived someday. is natasha still out there?
Haircomb is still chugging along, most of the general discussion happens in the Telegram channel.
You guys need a community page or a dedicated forum of some kind, I see a lot of memes and there is technical discussion on the telegram but there isn't much outreach for new users or engagement.
Its a shame haircomb is so niche now that interest with QR and scaleability is growing in the crypto community.
It would be nice to see some comb interaction with the bitcoin virtual machines or tokenisation projects to help onboard more people.
I don't understand some of the details of how liquidity stack works in Haircomb cryptocurrency. In the documentation it says that a stack is a construct, and "Constructs are stored off-chain in your wallet".
Is the stack object supposed to be created on the payer's or the payee's machine?
What happens when I send funds to a multipay stack which was created on another machine which is currently offline? Does it mean that all the payments that are defined by the stack will not happen until that machine is back online?
I have also seen in a discussion:
I didn't understand some details in this explanation.
How is the stack able to implement the transfer of the input funds to two addresses? I thought that in Haircomb we can only have no more than one directed edge coming out of an address.
I did not understand who "the observer" who decides when the stack should trigger is, and I did not understand the statement "all users do honor the rule." Does it mean that all users can see that the stack splits the input correctly? Does it not require that they could see the input amount (which should be hidden from most users)?
Or does it only refer to the user who owns the stack object? If so, why should we all trust him?
Is the stack object supposed to be created on the payer's or the payee's machine?
What happens when I send funds to a multipay stack which was created on another machine which is currently offline? Does it mean that all the payments that are defined by the stack will not happen until that machine is back online?
I have also seen in a discussion:
Quote
"Only if the amount at the liquidity stack input reaches the stack internal threshold, the observer considers that liquidity stack as triggered. After triggering, the threshold amount is moved to stack output, and a stack transaction connects the liquidity stack to liquidity stack change. If users didn't honor this rule then Haircomb couldn't function as a currency. That's why all users do honor the rule."
I didn't understand some details in this explanation.
How is the stack able to implement the transfer of the input funds to two addresses? I thought that in Haircomb we can only have no more than one directed edge coming out of an address.
I did not understand who "the observer" who decides when the stack should trigger is, and I did not understand the statement "all users do honor the rule." Does it mean that all users can see that the stack splits the input correctly? Does it not require that they could see the input amount (which should be hidden from most users)?
Or does it only refer to the user who owns the stack object? If so, why should we all trust him?
Haircomb, like Bitcoin, is a protocol; the best comparison is to a secret handshake. If someone attempts to do a secret handshake with you, but at step 5 instead of high fiving you they try to chestbump you, you won't go along with it because you know what the correct sequence of actions is. Haircomb is also a privacy coin; when your stack "triggers", the proof of the triggering is broadcast out, but only the relevant people can read it. When you validate a transaction history, you go through and check that the proof of a stack triggering is real, for the entire transaction history. You don't have to trust that it triggered, you require your counterparty to prove it to you. In order to know a stack has triggered, you need to know a) that the stack exists, and b) the amount of verifiable funds have been transferred into it.
The best comparison to BTC is looking at when you figure out which funds are where; because BTC is a public ledger, everybody who receives a BTC block immediately verifies the blocks contents and updates their record of who has what money. With Haircomb, rather than keeping a constantly updated database, you only ever calculate fund that you own/are about to own, and instead of doing it every BTC block, you do it whenever your balance is about to be updated. BTC works off of constant data processing, Haircomb works off of delaying the data processing for you until it's required.
As for how the stack can split funds while each wallet can only have one output; the stack is not a wallet. It's its own type of smart contract that operates using different rules.
hi, all
is this project still current? i'm looking for interesting ideas for quantum resistance and scaling on the bitcoin blockchain, haircomb is the only one that i remember but it seems pretty dead these days.
hope the project can be revived someday. is natasha still out there?
is this project still current? i'm looking for interesting ideas for quantum resistance and scaling on the bitcoin blockchain, haircomb is the only one that i remember but it seems pretty dead these days.
hope the project can be revived someday. is natasha still out there?
Haircomb is still chugging along, most of the general discussion happens in the Telegram channel.
hi, all
is this project still current? i'm looking for interesting ideas for quantum resistance and scaling on the bitcoin blockchain, haircomb is the only one that i remember but it seems pretty dead these days.
hope the project can be revived someday. is natasha still out there?
is this project still current? i'm looking for interesting ideas for quantum resistance and scaling on the bitcoin blockchain, haircomb is the only one that i remember but it seems pretty dead these days.
hope the project can be revived someday. is natasha still out there?
Combfullui 0.4.1 released. Users can upgrade if needed.
https://codeberg.org/watashi564/combfullui-0.4.0-bugfix/releases
Combdownloader 0.1.2 released. Upgrade is optional.
https://codeberg.org/watashi564/combdownloader-ng/releases
Combapp 0.0.7 released. Upgrade is optional.
https://codeberg.org/watashi564/combapp/releases
Users can newly install the haircomb full node as a docker container.
https://hub.docker.com/r/haircombs/haircomb
https://codeberg.org/watashi564/combfullui-0.4.0-bugfix/releases
Combdownloader 0.1.2 released. Upgrade is optional.
https://codeberg.org/watashi564/combdownloader-ng/releases
Combapp 0.0.7 released. Upgrade is optional.
https://codeberg.org/watashi564/combapp/releases
Users can newly install the haircomb full node as a docker container.
https://hub.docker.com/r/haircombs/haircomb
Combfullui 0.4.0 released. Users can upgrade if needed.
https://codeberg.org/watashi564/combfullui-0.3.8-features/releases
Combdownloader 0.1.1 released. Upgrade is optional.
https://codeberg.org/watashi564/combdownloader-ng/releases
Combapp 0.0.6 released. Upgrade is optional.
https://codeberg.org/watashi564/combapp/releases
As always, you can experiment with a live instance:
https://core.haircomb.org
https://codeberg.org/watashi564/combfullui-0.3.8-features/releases
Combdownloader 0.1.1 released. Upgrade is optional.
https://codeberg.org/watashi564/combdownloader-ng/releases
Combapp 0.0.6 released. Upgrade is optional.
https://codeberg.org/watashi564/combapp/releases
As always, you can experiment with a live instance:
https://core.haircomb.org
I don't understand some of the details of how liquidity stack works in Haircomb cryptocurrency. In the documentation it says that a stack is a construct, and "Constructs are stored off-chain in your wallet".
Is the stack object supposed to be created on the payer's or the payee's machine?
What happens when I send funds to a multipay stack which was created on another machine which is currently offline? Does it mean that all the payments that are defined by the stack will not happen until that machine is back online?
I have also seen in a discussion:
I didn't understand some details in this explanation.
How is the stack able to implement the transfer of the input funds to two addresses? I thought that in Haircomb we can only have no more than one directed edge coming out of an address.
I did not understand who "the observer" who decides when the stack should trigger is, and I did not understand the statement "all users do honor the rule." Does it mean that all users can see that the stack splits the input correctly? Does it not require that they could see the input amount (which should be hidden from most users)?
Or does it only refer to the user who owns the stack object? If so, why should we all trust him?
Is the stack object supposed to be created on the payer's or the payee's machine?
What happens when I send funds to a multipay stack which was created on another machine which is currently offline? Does it mean that all the payments that are defined by the stack will not happen until that machine is back online?
I have also seen in a discussion:
Quote
"Only if the amount at the liquidity stack input reaches the stack internal threshold, the observer considers that liquidity stack as triggered. After triggering, the threshold amount is moved to stack output, and a stack transaction connects the liquidity stack to liquidity stack change. If users didn't honor this rule then Haircomb couldn't function as a currency. That's why all users do honor the rule."
I didn't understand some details in this explanation.
How is the stack able to implement the transfer of the input funds to two addresses? I thought that in Haircomb we can only have no more than one directed edge coming out of an address.
I did not understand who "the observer" who decides when the stack should trigger is, and I did not understand the statement "all users do honor the rule." Does it mean that all users can see that the stack splits the input correctly? Does it not require that they could see the input amount (which should be hidden from most users)?
Or does it only refer to the user who owns the stack object? If so, why should we all trust him?
Combapp 0.0.4 available on F-Droid
https://f-droid.org/en/packages/org.bitbucket.watashi564.combapp/
New in version 0.0.4
CombApp 0.0.4
- New UI on port 21212
- RAM Pruning
- V2 Disk format (downgrade not possible after upgrade)
- Combdownloader 0.0.13
- Haicromb Core 0.3.7
Haircomb Core 0.3.7 available
Combdownloader 0.0.15 available with windows timers fix
Future development and all bitbucket repos will move on to:
https://codeberg.org/watashi564
https://f-droid.org/en/packages/org.bitbucket.watashi564.combapp/
New in version 0.0.4
CombApp 0.0.4
- New UI on port 21212
- RAM Pruning
- V2 Disk format (downgrade not possible after upgrade)
- Combdownloader 0.0.13
- Haicromb Core 0.3.7
Haircomb Core 0.3.7 available
Combdownloader 0.0.15 available with windows timers fix
Future development and all bitbucket repos will move on to:
https://codeberg.org/watashi564
Jump to: