Implement Segregated Witness (SegWit) P2WPKH/P2WSH Transactions for RVN and Assets

[m4r1m0]

BIP141 (https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki) describes adding a new structure called "witnesses" to "segregate" script and signature data from the rest of the transaction data. I propose implementing this for Ravencoin.

This would solve transaction malleability allowing for L2 micropayment channels such as Bitcoin's Lightning Network, as well as increasing overall scalability.

Scalability in particular will become an increasingly important issue to address as Ravencoin's asset-aware protocol allows for the creation of a near-infinite amount of tokens to be transacted on-chain.

[HyperPeek]

I like and support the idea although given the current strict implementation of rvn this will require another hard-fork.

[GiverofMemory]

I don't support this. There are other more straightforward ways to solve transaction malleability which is not a pressing issue regardless https://en.bitcoin.it/wiki/Transaction_malleability . Also in todays climate, only the blockchain counts, and sidechains especially for something critical like signatures, is a systemic risk.

Also Ravencoin has no reason for "increased capacity" of removing signatures from the blockchain as we have double the blocksize and 10x more blocks than bitcoin, and as such no use for lightning.