Implement efficient airdrops in split

[raphjaph]

This can either be done implicitly by recognizing that the split.yaml is airdropping the same amount to multiple outputs or explictly by introduction a mode in the split file called even or airdrop.

For reference #3658

[bingryan]

#3886

[kelven7224]

#3886

[kelven7224]

#3886

[dcorral]

What is the limit for a split?
How many outputs (aprox) can you fit in one split.yml?

[raphjaph]

Probably around 9000 P2TR outputs with 2 P2TR inputs and an 83 byte OP_RETURN

https://bitcoinops.org/en/tools/calc-size/

[blieb]

Was testing it on testnet, when I added more than 5 it did not fit in op_return anymore

when I did it with 100 outputs:
error: runestone size 3351 over maximum standard OP_RETURN size 83

[dcorral]

when I did it with 100 outputs: error: runestone size 3351 over maximum standard OP_RETURN size 83

Exactly.

What I really meant is how many explicit edicts can you add to a split file? I guess it depends on the amount size of the edicts?

[raphjaph]

Probably around 9000 P2TR outputs with 2 P2TR inputs and an 83 byte OP_RETURN

https://bitcoinops.org/en/tools/calc-size/

This is wrong, I was assuming a max standard size of 400000 Bytes but it's actually 100000 Bytes. So I think that would be around 2300 outputs.

What I really meant is how many explicit edicts can you add to a split file? I guess it depends on the amount size of the edicts?

At the moment the split file does one edict per entry so you reach the OP_RETURN standardness limit of 83 bytes after around 10 edict. If you do an even split you can however do less edicts. See #3658