Let this come to the notice of everyone; whoever got scammed should immediately report their case to the Internet Crime Complaint Center( ic3 ) they will help you recover your money back without collecting any fee. They helped me recover my money back on their denationalized refund campaign & I wasn't asked to pay any fees or charges. If you're a victim of romance or crypto scams, I'm open to sharing more details on how you can report your case to the ic3 with the possible hope of refunds (at least your capital back) without paying any fee or charge.

Hey!

Does any one knows why the counterparty API compose (testing MPMA) server. Return a much higher default sat/vb fee for a segwit address ? Resulting to a much overpaid transaction using the segwit address

You are specifying fee_per_kb? How far off is it?

It increase of ~40.4% increase

What encoding?

Mempool.space usually qualify the fees of non segwit as "optimal" while the segwit Overpay 4x

the auto one

https://api.counterparty.io:4000/v2/addresses/bc1qdqk5ruzu2v9dwd8cx0altuxewktefl3988qjwt/compose/mpma?assets=A900795585550900057%2CA900795585550900056%2CA900795585550910051&destinations=bc1qdqk5ruzu2v9dwd8cx0altuxewktefl3988qjwt%2Cbc1qdqk5ruzu2v9dwd8cx0altuxewktefl3988qjwt%2Cbc1qdqk5ruzu2v9dwd8cx0altuxewktefl3988qjwt&quantities=1%2C2%2C1&allow_unconfirmed_inputs=1&encoding=auto&validate=1&verbose=1

I’m at work right now so I can’t check in detail. Is this generating multisig outputs? If it is, then the sigops are also needed to determine the equivalent fee rate, which will end up being considerably higher than the actual sats/vb rate. Have you tried specifying taproot encoding? If you use taproot, remember that you also have to broadcast the reveal tx to finalize the counterparty tx (it comes presigned in the return json and should be broadcast after you sign and broadcast the tx)

Mpma with taproot encoding should be very inexpensive

https://api.counterparty.io:4000/v2/addresses/bc1qdqk5ruzu2v9dwd8cx0altuxewktefl3988qjwt/compose/mpma?assets=A900795585550900057%2CA900795585550900056%2CA900795585550910051&destinations=bc1qdqk5ruzu2v9dwd8cx0altuxewktefl3988qjwt%2Cbc1qdqk5ruzu2v9dwd8cx0altuxewktefl3988qjwt%2Cbc1qdqk5ruzu2v9dwd8cx0altuxewktefl3988qjwt&quantities=1%2C2%2C1&allow_unconfirmed_inputs=1&encoding=taproot&validate=1&verbose=1

Then I think the actual fee is btc_out+btc_fee because the btc_out is sent to the script used to store the data and the reveal tx consumes btc_out output as a fee to broadcast your tx as witness data.

Which in this case is 812 sats.

This is the same on freewallet, if you use 1 sat/VB fee, the second sat/VB tx fee is considerably higher so it’s cheaper to send 1 X 1

Atleast cheaper to send individually when the sat/VB fee is 1

I don’t know if freewallet sets the second fee rate automatically or it’s a protocol thing

damn never did that. Already a headache to sign witness

You sign the returned raw tx or psbt like normal, then wait a couple seconds and broadcast the signed reveal tx hex provided. With a large mpma, the cost will be quite low because all the addresses are stored in the witness data of the signed reveal tx and that storage costs 75% less. It should be cheaper than the previous P2SH encoding

I know I can change the minimum fee, but I’m talking about the multisend second fee, you can change that fee?

Do it again

You need to replicate it

That tx was 60+ days ago

Talking about it and not being able to replicate it at this point doesn’t do any good

Ikr, they're so BOTHERED....You basically can't say anything or post a meme. Don't talk shit. Its all serious business.
Meanwhile....the counterparty is broke.

It really is TOOFUNNY.

This one api call doesn’t seem to work. Address Credits

https://api.counterparty.io:4000/v2/addresses/13jM9iF3P3LzScBrNxtuBBxjGH7K8b8R1j/credits

It times out, once in a while it will show after a decent delay

This is cool

description changes show as "issuances" on tokenscan

https://tokenscan.io/tx/3050390
+
https://tokenscan.io/tx/3049273