Bitcoin Forum
July 07, 2024, 08:41:25 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Merged mining BU, Segwit  (Read 1225 times)
jubalix (OP)
Legendary
*
Offline Offline

Activity: 2618
Merit: 1022


View Profile WWW
May 24, 2017, 12:58:40 AM
Last edit: May 24, 2017, 08:02:16 AM by jubalix
 #1

Would there be any thing to stop merged mining Segwit or whatever BIP, and use the same address distribution as BTC?

Would this not make a natural outcome as to the best way?

No party has to compromise, you get your preferred unadulterated implementation

It avoids a hard fork, and allows whoever want to mine as they wish to upgrade as they wish?

I suppose updating with say development / innovation over time may be hard if you cannot attract enough devs, and the dev overload on say wallet changes / infrastructure change may be an issue, but still if it that much better good/popular solutions should attract enough of a following.

ETH / ETC shows a demonstration how this to works to some extent.

I think you would see BTC (now), BU and BTS (SEG) emerge, and each go to their price and utility, no one would be forced to join in or opt out.

It maybe I don't grok merged mining enough to say this but is seems a possibility to at least demonstrate the economic / network case.



Admitted Practicing Lawyer::BTC/Crypto Specialist. B.Engineering/B.Laws

https://www.binance.com/?ref=10062065
timisis
Member
**
Offline Offline

Activity: 178
Merit: 10


View Profile
July 01, 2017, 02:21:00 PM
 #2

How is it ETH ETC not a hard fork and a war even? Though I am not the knowledgeable person you asked for Smiley
italianMiner72
Hero Member
*****
Offline Offline

Activity: 910
Merit: 511


View Profile
July 03, 2017, 07:33:46 AM
 #3

we need just to wait to see what will be.
When a chain Forks... all could happen..
we will have the possibiliti to have not just 2 new coins but more.
This is realy important to be safe after fork: Having control of your bitcoins, who means having the most complete / total and absolute private key control. I mean all the Keys, are either single or multiple.

██▬▬▬

██▬

██▬

██▬▬▬



████           ▄▄█████████▄▄            ▄▄█████████▄▄        ████         █████      ██████████████████   ████████████       ████    ████████████    
████         ▄███████████████▄        ▄███████████████▄      ████       █████      ████████████████████  █████████████      ████    █████████████   
████        █████▀       ▀█████▄     █████▀       ▀█████     ████     █████         █       ████       █  ████     █████             ████     █████  
████       ████▀           ▀████▄   ████▀           ▀████    ████   █████                   ████          ████      ████     ████    ████      ████  
████      ████▀              ▀████ ▀███▀                     ████ █████                     ████          ████     █████     ████    ████     █████  
████      ████                 ████▄ ▀                       ████████                       ████          █████████████      ████    █████████████   
████      ████                  ▀████                        ████████                       ████          ████████████       ████    ████████████    
████      ████▄             ▄██▄ ▀████▄                      ████ █████                     ████          ████    ████       ████    ████            
████       ████▄           ▄████   ▀████▄           ▄████    ████   █████                   ████          ████    ▀████      ████    ████            
████        █████▄       ▄█████      █████▄       ▄█████     ████     █████                 ████          ████      ████     ████    ████            
████████████ ▀███████████████▀        ▀███████████████▀      ████       █████               ████          ████       ████    ████    ████            
█████████████  ▀▀█████████▀▀            ▀▀█████████▀▀        ████         █████             ████          ████        █████  ████    ████            

 
 
 
▬▬▬██

▬██

▬██

▬▬▬██
aesma
Hero Member
*****
Offline Offline

Activity: 2450
Merit: 929


fly or die


View Profile
July 06, 2017, 05:12:00 AM
 #4

Mining BU you will find BU blocks, you won't find BTC, and the reverse. "Merged mining" is not possible, it's like asking if you can catch freshwater fish and saltwater fish at the same time.
jubalix (OP)
Legendary
*
Offline Offline

Activity: 2618
Merit: 1022


View Profile WWW
July 26, 2017, 12:02:47 AM
 #5

Mining BU you will find BU blocks, you won't find BTC, and the reverse. "Merged mining" is not possible, it's like asking if you can catch freshwater fish and saltwater fish at the same time.

Presumably if the hash algo is the same eg SHA256, then you can use that output where you want, and submit to either chain, while slotting in different blocks, BU and BTC around that result.



Admitted Practicing Lawyer::BTC/Crypto Specialist. B.Engineering/B.Laws

https://www.binance.com/?ref=10062065
DannyHamilton
Legendary
*
Offline Offline

Activity: 3430
Merit: 4681



View Profile
July 26, 2017, 03:31:01 AM
Merited by ABCbits (2)
 #6

Presumably if the hash algo is the same eg SHA256, then you can use that output where you want, and submit to either chain, while slotting in different blocks, BU and BTC around that result.

The hash algorithm may be the same, but the input to that algorithm is NOT the same.

When working on a BTC block, the input is the 80 byte BTC block header dependent on the list of BTC transactions in that BTC block.

When working on a BTU block, the input is the 80 byte BTU block header dependent on the list of BTU transactions in that BTU block.

Since most BTU transactions won't be valid in the BTC blockchain, and most BTC transactions won't be valid in the BTU blockchain, it wouldn't be possible to have both 80 byte headers be identical (since they are both dependent on different lists of transactions). Therefore, the output for a BTU block won't be valid for a BTC block (or vice versa).
Pages: [1]
  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!