pull down to refresh

So basically I want to sell lukes fork coins from my cold wallets, which are secured by musig and shamir without the need to type my private keys into shady wallet forks.
The idea is to minimise risk by distilling everything to a single point of failure, split it and send all bitcoins back home to safety.
Here is how to do it:
First and most importantly you need a malware free system with a recent version of electrum. this is the single point of failure because we will create a jumpwallet, which will contain all our bitcoin for a short amount of time.

  1. create a new wallet in electrum & write down its seed. this is our jump wallet.
  2. move all your bitcoin to that new wallet. most impoirtant part is, that they need to move ON BOTH CHAINS.
    to make sure this worked fine you have to do the following for all your cold storage bitcoins:
  • create a tx which moves everything to the jump wallet.
  • then go to mempool.space and search for tx id. it will be found because you just broadcasted it.
  • now go to mempool.guide (Lukes fork version of the same page) and search for tx id as well. If its found, you are golden. coins moved on both chains.
  • if it is not found on ck to mempool.guide, which happened to me in most cases, go mempool.space. In the "Details" section, click the link next to "Transaction hex" and copy the hex. now go to https://mempool.guide/tx/push paste your tx hex into the first text area and click on "broadcast transaction" this way your tx is broadasted to the forked chain as well. if a red text appears next to the button something went wrong and it tells you what. if everything went fine you'll find you txid on mempool.guide as well, which means your forked coins moved.
  1. Now you have all your bitcoins and all your forked coins in your jumpwallet. whats left is creating a tx which is valid in bitcoin, but not on the forked chain. We will do that by sending all coins to ourself and add a op_return.
  2. in electrum, go to the "adresses" tab and copy the next free receiving adress of you jumpwallet. now go to the "send" tab, click "Tools" and select "Pay to many".
  3. enter whe following 2 lines into the "Pay to many" textbox:
    YOUROWNADRESS, !
    script(OP_RETURN aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa), 0

the syntax is simple, its target followed by amount, seperated by a comma. the exclamation mark means "everything in this wallet minus fees". So first line sends everything in the wallet to one of the wallets own adresses. the second lines sends 0 aka nothing, to an OP_RETURN output. what exactly you write into op_return is not relevant as long as its over 80 bytes of hex. hex is 0-9 and a-f, and 2 hex letters make a byte. so i simply went with 180 time the letter a to get a 90 byte op_return, which is not valid on the fork chain and will be rejected, while it confirms fine on bitcoin.
5. sign and broadcast et voila - you successfully splitted your coins. you can try to paste and broadcas the tx hex in https://mempool.guide/tx/push for fun but it won't work, because its not valid.
6. all thats left is move your bitcoins back to where they belong and wait for confirmations. now you can import the jump wallet or sweep its private keys into shady fork wallets and your bitcoin stays untouched. disclaimer: the airdrop-frenzy in 2018 teached me that shady fork wallets often contain malware so use them in isolated VMs only.

10 sats \ 1 reply \ @anon 3 Sep

One thing folks can eventually look forward to is taking delivery of bitcoin-SHA256 only coins when receiving on-chain bitcoin from various custodians/services and when closing lightning channels / requesting submarine swaps.

I sent some bitcoin-SHA256 (only) to a non-KYC custodian today to help get the party started. Helping the world of liquid bitcoin along next, it sucks that Boltz died but at least there are a few other services out there than can do smart contract swaps.

Bottom line, check your new UTXOs to see if you received bitcoin-SHA256 only. Every time you do is an opportunity to have an input that can be used with other send to self transactions to create deliberate splits. It's rewarding to actually spend and replace bitcoin vs just sitting on the pile.

Knowing bitcoin-SHA256 only UTXOs are coming your way is helpful for folks who are afraid of creating an unspendable output with the pay to many with OP_RETURN in the post here. (seems fine to me in theory, Electrum should take care to create a spendable output, Electrum also allows for to many where instead of that ! you put a small amount and it will then direct the rest to a change address)

Once one has a single spendable UTXO that is bitcoin-SHA256 only its possible to start consolidating all UTXOs to go even further on splitting ones own coins with self-sends in trusted wallets. But, folks should remember the privacy implications of consolidation as well, so personally I'm looking forward to taking possession of multiple bitcoin-SHA256 only UTXOs that can be paired with longer held UTXOs on self-spends. Done late enough in the game that won't be a pattern that ties UTXOs together as lots of people will routinely create transactions that spend bitcoin-SHA256 UTXOs in combination with mixed UTXOs.

Before self-sending a big UTXO some bitcoin-SHA256 only mixed in it may be worth while to construct, sign, but not broadcast a different self-send for a different target wallet that can be used for bitcoin-blake2b only purposes later. Electrum is good for this. Such transactions can be manually pushed into bitcoin-blake2b via the block explorer per this post at a later time when one feels confident that bitcoin-SHA256 utxos to elsewhere have already happened.

Folks with deeply protected vaults with big UTXOs should be careful about the approach here where they are potentially passing all coins through a wallet where their usual levels of security are not assured, for example temporarily downgrading a multi-sig to a single sig. Better perhaps to accumulate UTOXs that are bitcoin-SHA256 only and then use them later to facilitate shelf transfers from one secure vault to another.

reply
10 sats \ 0 replies \ @anon 5 Sep

Here's a safer procedure that doesn't involve running shady wallets:

  1. Create a throwaway Electrum wallet, and send $5 worth of BTC to it
  2. Do the scary pay-to-many transaction for that coin only with a destination address of your real wallet
  3. Now you have a SHA256-only coin in your real wallet!
  4. Create an annonymous account on the shady exchange, enable 2FA (needed later for withdrawal), generate a BTC2B deposit address, note it
  5. In the real Electrum wallet, create a transaction that sends all your coins (EXCLUDING the SHA256-only one!) to the deposit address
  6. Do NOT sign that transaction yet, just export it into a file
  7. In the real Electrum wallet, create a transaction that consolidates all your coins (INCLUDING the SHA256-only one!) into one (or multiple) change addresses
  8. Triple check everything is going to your own address, verify the color of the output (must be green/yellow)
  9. Sign and broadcast, wait for 6+ confirmations
  10. Now load the unsigned transaction from step 6, sign it, export it to clipboard
  11. Open mempool.guide in Tor Browser, click Broadcast Transaction, paste and broadcast
  12. You should see the deposit in the exchange, after about 6 confirmations, it will be tradable
  13. Sell for USDC (more liquidity) or BTC, withdraw (USDC through swap) to own wallet
reply
1 sat \ 6 replies \ @OT 2 Sep

Didn't the bip110 chain stall?

reply
10 sats \ 0 replies \ @anon 3 Sep

Correct, so the advocates pivoted to their hasty bitcoin-blake2a hardfork.

reply

Bitcoin continues, look at the mempool.guide. New algo (Blake2b replaced SHA-256d) for PoW started on Sunday. There has been the release of the Bitcoin Knots v29.4.1 yesterday.

reply
1 sat \ 3 replies \ @OT 3 Sep

Who killed the difficulty adjustment?

reply

The network deployed the improvement. Resilience.

reply
1 sat \ 1 reply \ @OT 3 Sep

The "network" or Luke?

Everyone could see this happening without replay protection and less than 1% of the hash rate.

reply

The network of thousands of nodes. There is the new signature hash type SIGHASH_UNIFIED which provides replay protection. Hash-rate is skyrocketing.

reply
95 sats \ 1 reply \ @Scoresby 2 Sep

Do you feel any concern about the privacy hit you take here? Moving all your coins in one tx might look like a consolidation (unless you are sensing to separate addresses -- which would be a royal pain in the ass). Maybe this is no big, but it's definitely something to think about. I'm curious what your approach is?

reply
113 sats \ 0 replies \ @fk OP 2 Sep

my approach is ignoring privacy implications. probably not smart but it is what it is...

reply

are those coins actually worth anyhing?

reply
11 sats \ 2 replies \ @fk OP 2 Sep

today trading opened on an exchange and prices are 100-200 usd per coin. however, the exchange is tiny, unknown and nobody knows if people can really cash out or its all a scam

reply

I'd guess it was set up with the sole purpose to do replay attacks

reply

wow that is a lot more than I would pay for them lol

reply

Yes, I bought 100m sats for 0.002 SHA256d-coin (equivalent of $160).

I will buy more for the exchange rate this week. Contact me if you are interested in a trade P2P.

reply

Don’t think I would ever do this.

reply
1 sat \ 0 replies \ @deSign_r 2 Sep -100 sats

Today's Best Website Design

Paul Kalkbrenner by HOLOGRAPHIK

https://m.stacker.news/154653
#1560787