Bitcoin Forum
May 07, 2024, 07:37:48 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 7 8 9 10 [11] 12 13 14 15 16 17 18 19 »  All
  Print  
Author Topic: [ANN][COMB] Haircomb - Quantum proof, anonymity and more  (Read 6886 times)
natasha-otomoski (OP)
Copper Member
Jr. Member
*
Offline Offline

Activity: 82
Merit: 5


View Profile
June 03, 2020, 05:58:11 PM
 #201

To claim combs you need to generate your key and then view it's stealth
addresses - you will see your long bitcoin mine addresses.

Simply tip 546 sats to successive mine addresses every time a block is mined.

Don't forget to fully save your wallet from the main page to a file.


To see your coins you need to sync using the modified bitcoin core.



About exchanges - we aren't listed anywhere yet, but it is not a huge problem
because the coin offers a comb trade facility, basically enabling something
similar to a decentralized exchange or an escrowing. The swaps are atomic as
long as the "decider person" is honest and even a dishonest "decider person" cannot
do much harm.

Comb trade can also be used for fair peer to peer bets (gambling)






This is a privacy coin.




My educated guess. Price is currently known to be anywhere between $1 and $10.
Market cap is on the order of $5000- $50000. There is about 5000 spendable coins.

If you see a higher figure about the spendable coins, this is because coins
before the first block could also be counted but they are provably burned.
(All the way back to the segwit start)
Another fact is that many Bitcoin users pay to the long addresses and unknowingly
burn newly generated COMBs, these COMBs are also provably lost as the
cryptography of Bitcoin used to generate ordinary bitcoin keys is very different.

These random users are forming the price floor.


There is no premine. (0 COMB is premined, I've claimed just like an ordinary user would)



The coin runs on the Bitcoin chain and provides roughly same degree of finality
of transactions.
1715110668
Hero Member
*
Offline Offline

Posts: 1715110668

View Profile Personal Message (Offline)

Ignore
1715110668
Reply with quote  #2

1715110668
Report to moderator
You can see the statistics of your reports to moderators on the "Report to moderator" pages.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715110668
Hero Member
*
Offline Offline

Posts: 1715110668

View Profile Personal Message (Offline)

Ignore
1715110668
Reply with quote  #2

1715110668
Report to moderator
1715110668
Hero Member
*
Offline Offline

Posts: 1715110668

View Profile Personal Message (Offline)

Ignore
1715110668
Reply with quote  #2

1715110668
Report to moderator
1715110668
Hero Member
*
Offline Offline

Posts: 1715110668

View Profile Personal Message (Offline)

Ignore
1715110668
Reply with quote  #2

1715110668
Report to moderator
CryptoFamBoy
Newbie
*
Offline Offline

Activity: 14
Merit: 1


View Profile
June 03, 2020, 07:58:13 PM
 #202

Is there any possibility to buy this coin without setting up any special node? (I am ready to use some alpha-wallet though)
kelozar
Newbie
*
Offline Offline

Activity: 71
Merit: 0


View Profile
June 04, 2020, 01:53:11 PM
 #203

You can generate Comb address using wallet. But to be able to prove you received the comb, you would need a full node fully synced.
CryptoFamBoy
Newbie
*
Offline Offline

Activity: 14
Merit: 1


View Profile
June 04, 2020, 07:17:34 PM
 #204

Well, I think there is definitely a possibillity to check the receiving of coins through some trusted full node owner. I would like to buy some coins after (and if) the situation in the https://bitcointalk.org/index.php?topic=5252297.0 is cleared.
natasha-otomoski (OP)
Copper Member
Jr. Member
*
Offline Offline

Activity: 82
Merit: 5


View Profile
June 05, 2020, 08:08:43 AM
 #205

Hello I've just released combfullui 0.3.3 open source on github.

Please make sure you have a copy.

I'm officially stepping down from the position of the lead developer.
My part of project seems complete and I will be happy to help
or watch others develop their own improved versions.


Thanks for your attention.

7cb6b988a4431db586979e3714751dc8ad934c89276955dd8a5157ed607529cd  PUBLIC_DOMAIN
49d5f5ec5b37a7ae9512148237c03068ee8f5d6c282c0cd0bb8f3017ebc3e0ed  anonminize.go
2808b6f4a6cff6362dceae04588c6eb194728f1d5184cce210fb44f5f63f0a2b  balance.go
6e37b41734eadd032a533a98a8f1c198f1d34f9afe136b278aab4c76cc4e9827  basic_contract.go
3dbe40b7860ea7d4caa396b5221ea636aaf08e8513521bbc04a0a88ae3e208aa  coinbase.go
0885da61b260e8b6dee54d73cde806c5f4007588a6bad082500f4c5085f31850  commitfile.go
517646c621a628d30e9cac103259fa6a47b145c92df579cbdbf1858bfb8f372a  commitment.go
53f119c27580daf40cd5c916d9fae3c037e58a9dda5f0a017e5ada268fb9461c  corruption_bisect.go
38d14c41508ca33975a63274950bdb5846a056b52fd53c4701db516a872d822c  cutwhere.go
53b261ccb57928dc5ba02fc0415a9a1769fa6ae608fe6a8e336e73f5fac0dd31  deciders_purse.go
e103b4f22d4a7bb539c81978ad9bb80d1ec47e0041e54902e9c40745ee38849e  deployment.go
7257186ac82b85e4cb58b8b17cb75de14028cadc3860741527d0cc6bff618dcb  dummyhttpwriter.go
b27f6aee1c1fb97a0b5b5a5cc942fba37656ba40f842fdb20aad51ca7def0dc0  export.go
cddc3bd767ef47ea828abaecd5a3d4622bf640db17e03de583648e6566b08a27  hexutil.go
5097b8d29f4ae30040d90ccafe9c759ba5385b0f006e7b979c30d6375f78e578  import.go
e4d2e000da8368a60a48ec7649f44ca94bb69bdbd8101efdc9be3aeb30c6821e  loopdetect.go
e2fa75c079b0b65bae7d3b23991da53c0f96afa98a9b28e4342146d2e1b70c1c  main.go
4647d5f90ae0b32755c96b33775176cc0c745bf8d27e704a4a7d5cebd9ff7826  mainpage.go
bd5ec8ab0815c9fae1b614e610d4f815ff56d1f591f1084a64f3793ae51fdcaa  merkle.go
68994237974102ea653537f923356decf6865be8c8a9cdc5d360cd3310ee8f4e  mine.go
19bb0e30bcf9488135f5134f33e0f18285fbf7d51ce702a4f3f19e35727d8a84  resetgraph.go
0b95c2afc533395db38fa8028d854e1b0f94508717888fee76eb4c138ef18f69  segmentmerkle.go
8120719d4fb1059ad657df54ad6ff40f9a247f8d136d2305f2072e81a17c4f85  segmentscoinbase.go
7b70655a65d0d3021447123f0f6e70f1fd07b13b4c41461ca9e86be0dbced4f3  segmentstack.go
53d677c9d05c61c8b87c026dd08bbda7b038eeae44d6dc5d3a0d1fe51db0375e  segmenttx.go
bd40a2100146b553c40c649b9461eed4fbd2e02297fef64e20212e673970fe61  sign.go
1c50c9ba0025569c57d2164612d71f7a24a07cb32b2d0897511ff1937015419e  stackbuilder.go
28a9c0198f47a9272f1580361601ab16b911ba4d5c961b680685327e34cbe122  stack.go
f33dbfe4a588366bd93108b4f31dde50ff456f882c74be2334fdff2b98651cf7  stackgui.go
21209fbce1077b646c5e18a4366f3a1cba822a480e6c416ccf8a7c899e7bacad  stealthgui.go
a23cde6642f7e622d7d88cdabbbc076e99e820b0d0f3f9d45f044b91a8c38c9d  txlegs.go
543b579c8ad8736a664a58a67ef88802e006290cefd841611bd53d34ea271e73  txrecv.go
4f1785c385e9301553497bb4158e33c560cc3b1305993a6990e9289b2ee86e59  used_key.go
732f71d1138e749a35bed6b9f1121c1c1d2698372161bf0cfc7ce9ba1896793f  utxo.go
ddf07711f28c1b164c495973f29d5227139ed89ef135bace47faf794bca9c482  utxotag.go
6a56339fc3aeee574a51bf363d3188270df36f7b153f71d29a9853c74e366b4c  wallet.go
kelozar
Newbie
*
Offline Offline

Activity: 71
Merit: 0


View Profile
June 05, 2020, 03:31:22 PM
 #206

Hello I've just released combfullui 0.3.3 open source on github.

Please make sure you have a copy.

I'm officially stepping down from the position of the lead developer.
My part of project seems complete and I will be happy to help
or watch others develop their own improved versions.


Thanks for your attention.

7cb6b988a4431db586979e3714751dc8ad934c89276955dd8a5157ed607529cd  PUBLIC_DOMAIN
49d5f5ec5b37a7ae9512148237c03068ee8f5d6c282c0cd0bb8f3017ebc3e0ed  anonminize.go
2808b6f4a6cff6362dceae04588c6eb194728f1d5184cce210fb44f5f63f0a2b  balance.go
6e37b41734eadd032a533a98a8f1c198f1d34f9afe136b278aab4c76cc4e9827  basic_contract.go
3dbe40b7860ea7d4caa396b5221ea636aaf08e8513521bbc04a0a88ae3e208aa  coinbase.go
0885da61b260e8b6dee54d73cde806c5f4007588a6bad082500f4c5085f31850  commitfile.go
517646c621a628d30e9cac103259fa6a47b145c92df579cbdbf1858bfb8f372a  commitment.go
53f119c27580daf40cd5c916d9fae3c037e58a9dda5f0a017e5ada268fb9461c  corruption_bisect.go
38d14c41508ca33975a63274950bdb5846a056b52fd53c4701db516a872d822c  cutwhere.go
53b261ccb57928dc5ba02fc0415a9a1769fa6ae608fe6a8e336e73f5fac0dd31  deciders_purse.go
e103b4f22d4a7bb539c81978ad9bb80d1ec47e0041e54902e9c40745ee38849e  deployment.go
7257186ac82b85e4cb58b8b17cb75de14028cadc3860741527d0cc6bff618dcb  dummyhttpwriter.go
b27f6aee1c1fb97a0b5b5a5cc942fba37656ba40f842fdb20aad51ca7def0dc0  export.go
cddc3bd767ef47ea828abaecd5a3d4622bf640db17e03de583648e6566b08a27  hexutil.go
5097b8d29f4ae30040d90ccafe9c759ba5385b0f006e7b979c30d6375f78e578  import.go
e4d2e000da8368a60a48ec7649f44ca94bb69bdbd8101efdc9be3aeb30c6821e  loopdetect.go
e2fa75c079b0b65bae7d3b23991da53c0f96afa98a9b28e4342146d2e1b70c1c  main.go
4647d5f90ae0b32755c96b33775176cc0c745bf8d27e704a4a7d5cebd9ff7826  mainpage.go
bd5ec8ab0815c9fae1b614e610d4f815ff56d1f591f1084a64f3793ae51fdcaa  merkle.go
68994237974102ea653537f923356decf6865be8c8a9cdc5d360cd3310ee8f4e  mine.go
19bb0e30bcf9488135f5134f33e0f18285fbf7d51ce702a4f3f19e35727d8a84  resetgraph.go
0b95c2afc533395db38fa8028d854e1b0f94508717888fee76eb4c138ef18f69  segmentmerkle.go
8120719d4fb1059ad657df54ad6ff40f9a247f8d136d2305f2072e81a17c4f85  segmentscoinbase.go
7b70655a65d0d3021447123f0f6e70f1fd07b13b4c41461ca9e86be0dbced4f3  segmentstack.go
53d677c9d05c61c8b87c026dd08bbda7b038eeae44d6dc5d3a0d1fe51db0375e  segmenttx.go
bd40a2100146b553c40c649b9461eed4fbd2e02297fef64e20212e673970fe61  sign.go
1c50c9ba0025569c57d2164612d71f7a24a07cb32b2d0897511ff1937015419e  stackbuilder.go
28a9c0198f47a9272f1580361601ab16b911ba4d5c961b680685327e34cbe122  stack.go
f33dbfe4a588366bd93108b4f31dde50ff456f882c74be2334fdff2b98651cf7  stackgui.go
21209fbce1077b646c5e18a4366f3a1cba822a480e6c416ccf8a7c899e7bacad  stealthgui.go
a23cde6642f7e622d7d88cdabbbc076e99e820b0d0f3f9d45f044b91a8c38c9d  txlegs.go
543b579c8ad8736a664a58a67ef88802e006290cefd841611bd53d34ea271e73  txrecv.go
4f1785c385e9301553497bb4158e33c560cc3b1305993a6990e9289b2ee86e59  used_key.go
732f71d1138e749a35bed6b9f1121c1c1d2698372161bf0cfc7ce9ba1896793f  utxo.go
ddf07711f28c1b164c495973f29d5227139ed89ef135bace47faf794bca9c482  utxotag.go
6a56339fc3aeee574a51bf363d3188270df36f7b153f71d29a9853c74e366b4c  wallet.go


can you upload compiled version as well like before? thanks
kelozar
Newbie
*
Offline Offline

Activity: 71
Merit: 0


View Profile
June 06, 2020, 12:04:30 PM
 #207

i would like to let everyone know that might not already
if you are looking to claim some combs and want to use less amount of satoshi
right now is one of the most optimal times
hashrate is increasing, that means blocks are found on average faster then 10mins
this leads to much lower fees on average
here is good site for hashrate
https://diff.cryptothis.com/
and these sites are good for mempool information
https://jochen-hoenicke.de/queue/#0,1w
https://mempool.space/

if anyone would like i can sell them some comb and claim some more to replenish, with a small fee for my time and fee to pay for the transfer (fund 21 tx's onchain)
its very possible to claim for an average of about 50k-100k satoshi per comb at the moment.
CryptoFamBoy
Newbie
*
Offline Offline

Activity: 14
Merit: 1


View Profile
June 06, 2020, 12:15:09 PM
 #208

@kelozar Wasn't it about 500 satoshi to claim a COMB? Why did it increase to 50000, which is 100 times more? Almost 5$ is pretty expensive for a new, unknown coin. 

I also would like the natasha (if it's her/his real name) to elaborate on the fake photo problem and why is she leaving the dev position now, at the stage where the project is not even close to the 1.0.0 stage?
kelozar
Newbie
*
Offline Offline

Activity: 71
Merit: 0


View Profile
June 06, 2020, 12:36:39 PM
 #209

@kelozar Wasn't it about 500 satoshi to claim a COMB? Why did it increase to 50000, which is 100 times more? Almost 5$ is pretty expensive for a new, unknown coin. 

I also would like the natasha (if it's her/his real name) to elaborate on the fake photo problem and why is she leaving the dev position now, at the stage where the project is not even close to the 1.0.0 stage?

it is 546 satoshi to the mining address. but to successfully claim, you need to be the first new unseen p2wsh transaction in the block. (only 1 successful claim per btc block)
currently most miners organize the transactions with highest fee first. not all miners and not always, but more times then not aside from exceptions.
because alot of exchanges have some type of outputs that almost always have a new p2wsh tx in their batches for some reason. this means you need to pay higher fee then they do in order to be the first.
when the blocks are found longer then 10mins, there is a competition and other exchanges pay higher for some reason.
when the blocks are faster then 10 mins. it is possible to pay less (sometimes) and still be the first unseen p2wsh output, but not always.

the 50k is due to several things, first its the fee used to be the first p2wsh, 2nd is because sometimes you pay the fee but the miner included another transaction before yours in the block. also sometimes before the block is found you see higher fee being broadcasted so you are forced to either up your fee (and hope they dont use the previous broadcast), or up your fee and still not be the first for whatever other reason.
aside from this in order to transfer comb from 1 address to another, you need to fund 21 of those 546 transactions, which also cost fees.
also i am doing this all manually, so i am manually monitoring the mempool and this is time intensive as well as cost satoshi which doesnt even guarantee a claim.

dont get me wrong, there is times you can claim for 15k satoshi successfully, but there is times it could cost 100k+ to claim successfully, there is ways to try to lower your avg but due to things outside ones control you cant really be guaranteed anytime (atleast from what i have learned so far)

as far as the real name and photo
natasha otomoski is an anagram for satoshi nakamoto, (re-arrange the letters)
the photo is obviously fake but i assumed everyone knew that? if the creator is using an anagram of satoshi, and said they are using tor, they obviously care about their privacy.
so why would they put a real photo? also the photo is like a stock photo found online. its not even hard to find it. it was obvious to anyone RIGHT AWAY that this is not a real name nor real photo.

take it as you will, im not endorsing this project or vouching for the dev or the project. i am just experimenting here like everyone else.
hope this explains your questions, if you have any others dont hesitate to ask, i will help however i can

thats my 2combs.
BlackR4ptor
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
June 10, 2020, 03:09:59 AM
 #210

@kelozar Wasn't it about 500 satoshi to claim a COMB? Why did it increase to 50000, which is 100 times more? Almost 5$ is pretty expensive for a new, unknown coin. 

I also would like the natasha (if it's her/his real name) to elaborate on the fake photo problem and why is she leaving the dev position now, at the stage where the project is not even close to the 1.0.0 stage?

Were you successful in claiming COMB without having to spend more than 546 satoshi? I´m willing to do all the install and sync process, but I agree $5 is too expensive for a unknown coin.
Fizbann
Newbie
*
Offline Offline

Activity: 11
Merit: 0


View Profile
June 10, 2020, 12:46:55 PM
Last edit: June 20, 2020, 07:49:28 PM by Fizbann
 #211

@kelozar Wasn't it about 500 satoshi to claim a COMB? Why did it increase to 50000, which is 100 times more? Almost 5$ is pretty expensive for a new, unknown coin.  

I also would like the natasha (if it's her/his real name) to elaborate on the fake photo problem and why is she leaving the dev position now, at the stage where the project is not even close to the 1.0.0 stage?

Were you successful in claiming COMB without having to spend more than 546 satoshi? I´m willing to do all the install and sync process, but I agree $5 is too expensive for a unknown coin.

This has been explained plenty of times, but let's try again.

To make a successful claim, you need to tip at least 546 sats (no more are needed) to a new stealth address from your COMB wallet and that transaction must be the first one mined on the block with an unseen P2WSH output address.

If you are doing transactions with the only intent of claiming COMB the price is far from 546 sats since the fee of the transaction must be included on the price of the token.
The fee can range widely from the minimum fee possible for a transaction to be completed or as high as you want it to be to ensure the claim.

As kelozar says, currently the average COMB claiming transaction is paying ~50k in fees.
Usually, the longer a block is the bigger is the fee of the claiming transaction and the opposite happens on shorter blocks. But that's not a rule.

I think a fair price per COMB should address:
  546 sats tipped to a stealth address
+FEE accounting for the sats paid to be the claimer tx
+TIP since not all the claim attempts are successful

However, you could claim way cheaper COMBs. If you were making a regular BTC transaction you could include a tip to a stealth address so you have an 'almost free' chance to claim.

To make a COMB payment you need to fund 21 addresses with 546 that should also be included on the total transaction, not per COMB.

As for me, when claiming I usually waited 8-10 minutes of block time and then sent a transaction with a small increase in fees over the current claimer, as long as it wasn't higher than 60k sats. Most of the claims were made between 40k and 50k. Very few were achieved with <30k

Please, someone, correct me if I am wrong.
natasha-otomoski (OP)
Copper Member
Jr. Member
*
Offline Offline

Activity: 82
Merit: 5


View Profile
June 10, 2020, 05:32:35 PM
 #212

Please note that my 546 sats recommendation is not a hard rule. In fact
amounts as low as 330 sats per output might be practical for ordinary users.


546 sats is only quoted because many sites quote it and it appears to be working
fine and the transactions did not have problem getting relayed or anything else.


It all depends on how dust is defined by the Bitcoin client and I have no
intention whatsoever to influence those rules. Please respect the Bitcoin rules.


Another concern about the 546/330 amount is that I am strongly convinced that
every Haircomb user needs to use the same amount for privacy reasons, to blend
into the crowd of other Haircomb users.


This means the migration to 330 sat claiming amount should be flag-day, if done.

natasha-otomoski (OP)
Copper Member
Jr. Member
*
Offline Offline

Activity: 82
Merit: 5


View Profile
June 12, 2020, 09:09:22 AM
 #213

To compile haircomb core from source please do the following:


Download and install google go language from https://golang.org

Download and install git bash https://git-scm.com/downloads


Next, open git bash a black command window will appear.

Use these commands

Code:

cd Documents

git clone https://github.com/natasha-otomoski/combfullui.git

cd combfullui

go get github.com/gorilla/mux

go get github.com/sipa/bech32/ref/go/src/bech32

go build

start .


After this there should be folder combfullui in your Documents with combfullui.exe appeared inside

Please replace your old combfullui.exe with this new one.


kelozar
Newbie
*
Offline Offline

Activity: 71
Merit: 0


View Profile
June 12, 2020, 09:47:05 PM
 #214

when i try
go get github.com/gorilla/mux
it says
bash: go: command not found
natasha-otomoski (OP)
Copper Member
Jr. Member
*
Offline Offline

Activity: 82
Merit: 5


View Profile
June 13, 2020, 07:38:13 AM
 #215

Open control panel
Open System and Security
Open System
Open Advanced system settings
On the left open Advanced tab
Open Environmental Variables
Select System variables Path
Click Edit
Add new row "C:\Go\bin" (this must be the folder where go.exe was installed)


Close and open git bash again, run commands again without the git clone step that is already complete.


Code:
cd Documents

git clone https://github.com/natasha-otomoski/combfullui.git

Code:
cd combfullui

go get github.com/gorilla/mux

go get github.com/sipa/bech32/ref/go/src/bech32

go build

start .
kelozar
Newbie
*
Offline Offline

Activity: 71
Merit: 0


View Profile
June 13, 2020, 04:44:10 PM
 #216

followed the steps, interesting to note i already had C:\Go\bin in the variables.
so i gave it another try, and everything worked.

success, running  the new comb0.3.3

thanks for helping
kelozar
Newbie
*
Offline Offline

Activity: 71
Merit: 0


View Profile
June 15, 2020, 03:17:08 AM
 #217

I am proposing we switch to 330 satoshi claims and 330 satoshi fund for transaction.
This will be good reduction in cost to send comb.
If anyone objects please tell us why. Otherwise lets all agree to 330 satoshi. If in future miners and wallets default less we can switch again.
Fizbann
Newbie
*
Offline Offline

Activity: 11
Merit: 0


View Profile
June 15, 2020, 08:08:53 AM
 #218

I am proposing we switch to 330 satoshi claims and 330 satoshi fund for transaction.
This will be good reduction in cost to send comb.
If anyone objects please tell us why. Otherwise lets all agree to 330 satoshi. If in future miners and wallets default less we can switch again.
Yay, for my part
natasha-otomoski (OP)
Copper Member
Jr. Member
*
Offline Offline

Activity: 82
Merit: 5


View Profile
June 16, 2020, 06:25:56 AM
 #219

ok we can do it starting from block 636363.


By the way I've been contacted by an undisclosed person who is willing to acquire
a 3 BTC worth of Haircomb token. I told the person to claim on the free market, but
out of interest, would anyone be willing to fill such an order?


The way I see it 3 BTC may well be worth more than the entire supply.
Fizbann
Newbie
*
Offline Offline

Activity: 11
Merit: 0


View Profile
June 16, 2020, 09:14:13 AM
 #220

ok we can do it starting from block 636363.


By the way I've been contacted by an undisclosed person who is willing to acquire
a 3 BTC worth of Haircomb token. I told the person to claim on the free market, but
out of interest, would anyone be willing to fill such an order?


The way I see it 3 BTC may well be worth more than the entire supply.

I am willing to pool some of mine

Pages: « 1 2 3 4 5 6 7 8 9 10 [11] 12 13 14 15 16 17 18 19 »  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!