Hi
Haircomb on litecoin is a possibility, it will be a separate coin (only on Litecoin assuming that's what you want).
I will just briefly write what is the minimal effort you need to do in order to kickstart such a coin.
First of all you need a white paper preferably you put some recent LTC block-hash into the
whitepaper to prevent a premine.
Briefly explain in your whitepaper the subsidy formula at minimum so that people at least
know how many tokens they claimed by a valid claim on a block.
You can code any subsidy formula in coinbase.go just recode the Coinbase(height uint64) function.
Just make sure there is not some kind of numeric overflow in 64bit monetary amount when you add too many subsidies to one wallet.
Next take SHA256(whitepaper.pdf) and put that into commitment.go file.
Next to actually claim you need to modify bech32get in sign.go to match litecoin format. I think just change "bc" to "ltc"
Recompile combfullui.exe
Next you can start modifying litecoin core. You need to modify it in the same manner the Natasha
modified bitcoin core.
Each time a block is added to a litecoin longest valid chain you need to call (for every long ltc address in the block)
the following endpoint of haircomb core.
http://127.0.0.1:2121/mining/mine/{commit}/{utxotag}also at the end of block you need to call it one more time to flush it.
The flush comand has arbitrary 256bit commit (for instance FFFFFF... it's not used for anything) but it must have utxotag = 9999999999999999
You can be loading the commitments in the following manner:
suppose there was address funded on litecoin chain:
ltc1qguz6pay8hvv0qsd07wtptcfx5wjxa8tqququgurlvm2yfaj9txqsn8xsdv
mined for example in block 1673450
Now when your litecoin core adds this block to his longest valid chain the above address (output) in hex:
00204705a0f487bb18f041aff39615e126a3a46e9d600701c4707f66d444f6455981
you discard the 0020 from the beginning and call over http (also it needs to be uppercase because Natasha hated lowercase):
http://127.0.0.1:2121/mining/mine/4705A0F487BB18F041AFF39615E126A3A46E9D600701C4707F66D444F6455981/0167345000000001the 00000001 at the end is some kind of iterator I think recent combfullui.exe after fork does not even use it for anything so
you can supply 0,1,2,3 from the block or whatever (which one long address inside the block it was) it just must be unique
then you flush it:
http://127.0.0.1:2121/mining/mine/FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF/9999999999999999and now this commitment appears in the litecoin commits.db file (but only if the address was funded the 1st time!) and triggers
any transactions in the wallet that require it.
But you need to be loading blocks in the correct order obviously. You can't load block 123 and then 122.
Recompile litecoin core and sync it.
Go into your wallet generate a key and claim some litecomb. Fully save your wallet. Good luck.
Now there are many ways that can go wrong if this gets widely used and I don't actually encourage to do this.
For instance somebody can pay from litecomb key and somebody can replay that payment to haircomb on bitcoin.
secondly people can confuse addresses, pay litecomb to normal haircomb address and get glued coins
the coin can pump and dump and never recover causing financial loss
and many more things
but it will work for experimental purposes.
Cool, thank you for taking the time to explain how this would be done. It's beyond my coding ability but I will try to work through the process and see how far I get.
Show Posts
