Understanding datacarrier and permitbaremultisig Settings

I got a node that's connected and it has commands in the User Agent field... Anyone know if setting datacarrier to 0 and permitbaremultisig to 0 is safe? What do they actually do?

Yeah man, that’s all about the config file! Been running my node on Windows 11 with the.conf in a different drive. Found it in E:\Bitcoin and it works as expected.

From what I know, datacarrier=1 lets you send transactions with OP_RETURN, and permitbaremultisig=1 lets you do multi-signature transactions with P2MS. That’s just how Bitcoin Core operates by default, so not sure why some nodes flag it as spam.

Good point, I’m also curious about this. Waiting for some solid answers.

Ordinals are part of that default behavior too, but some mining pools filter them out. On the topic of multisig, if you do like a 1-of-20, you just need one valid key and the rest can be junk data.

This sounds more like a pro argument. Waiting to hear counterpoints.

True, Bitcoin Knots and some pools like Ocean can ditch Ordinals. They’re a small bunch trying to push back against it. The GitHub links mention P2MS for tokens, but that’s kinda fading now. I don’t see why we’d need to reject bare multisig.

Depends on your setup. If you’re handling a lot of multisigs, you got more hashing to do, which could make cheaper transactions more appealing. Just saying, it might be more profitable.

If your block isn’t easy to validate, stale blocks are a risk. Miners will be competing to validate and it could mess with your timing.

Configuring your node to reject transactions that most nodes accept just bloats bandwidth and slows block propagation. Compact blocks rely on shared mempool transactions.

Seems like that advice is a bit off. It feels more like a way to cut down on 'junk' transactions.

They’re not junk tho, they pay miners. Every fee counts.

Anyone know if there’s a way to broadcast a transaction with permitbaremultisig=1 outside of Core or Electrum? I need to clear out some multisig outputs.

Check out MARA Slipstream. They accept a lot of non-standard TX in blocks they mine. But yeah, you’ll need to make the TX with their fee rate.

I saw that, but now you need a client code to use their service. I’ve written a Python script to spend odd multisig outputs, but some aren’t recognized anymore.

Isn’t the default still permitbaremultisig=1? I thought that PR to disable it wasn’t merged. People say P2MS is still being created.

Oh wow, I messed that up. I can spend some outputs but not all, even if they look the same.

The error is probably due to inputs being missing or already spent. Not exactly about P2MS standards.

I can see those outputs on mempool.space, but can’t spend them through Core’s service because they follow default rules.

The error message should be different if it was a P2MS issue. You’re spending from the UTXO, not creating new outputs, so it shouldn’t matter.