Adding to that it would be great if someone comes up with a solution (right now I have not found one) to consolidate several paper wallet private keys into one wallet and send it safely to the burn address. Doing that in omniwallet.org is not my first choice (main reasons: online wallet, beta stage software, not in active deveopment for many years).
Omni works on singular addresses.
The wallet you choose will be importing the private keys and you need BTC in each address for the OMNI protocol
If you are doing the sign and burn then the problems of online wallet are minimal and very unlikely to be any issue. Import private key, sign, then burn.
Omniwallet.org works fine
There is one hardware wallet that can operate OMNI and generate the transactions
2 Likes
Thanks for the explanation!
I was hoping to be able to import all paper wallets into one omniwallet.org (if there is no other solution) and being able to send with only one BTC transaction for the single wallet to pay for the fees. It seems this is not the case. This is very unfortunate and means I need to fund each and every paper wallet address with BTC first (without knowing how much is needed exactly and with associated high on-chain fees).
Bummer!
I think it’s a good solution; allows the maid to get out of the market through the burn; and a simple swap through message signing 
btc fees have always been a known weak point of omni; emaid swap wasn’t cheaper and the feeless swap might be able with the direct swap to native then I guess =)
3 Likes
Yes that can be done
I would expect the burn process requires you to be sending the OMNI MAID from one address to a burn address as a separate process so that it can be verified by the smart contract
You can do the transfer setup in omniwallet.org and it will give you the BTC amount required. You can also change the fees needed which will affect transfer time.
So even though the fee might change from minute to minute, it will be approx the same and you can adjust the fee before sending if you do not quite have enough.
Thus this method would be to start a send transaction and find out the BTC needed then transfer that amount of BTC into the address and then go back and do the transaction, adjusting the fee if its now slightly higher.
Another method that is probably easier and less steps is to transfer more than enough BTC into the first address, do the sign and burn, then transfer the left over BTC into the next address and do the sign & burn, and then transfer remaining BTC into the 3rd address repeating the process and on the last one transfer the left over BTC to where ever you want
This is one reason I preferred snapshot, but its really just saving the dollar transfer fee, and less steps needed.
1 Like
Is this on 100 percent, that bitmart will not accept new token…? If somebody hold here? I dont ask for me
If bitmart has not officially said they will do something then just know that if you do not have the private key to your MAID then you have no MAID to transfer.
Bitmart is trading EMAID fwiw, not MAID.
4 Likes
Thanks again for the detailed explanation.
I will then probably have to live with that and do it step by step with every paper wallet like you described. Now just for fun imagine doing that for a large number of paper wallets - let’s just say large enough to think about automating it. 
It would be nice to understand why it was decided to not go with a snapshot solution for MAID holders (technical reasons?) like it seems to be possible for the eMAID holders.
1 Like
And with the snapshot exchange to ANT for eMAID then its best to get your eMAID into your own controlled address quick smart
1 Like
Its a little more complex I guess.
Also there are a number of people with their OMNI MAID not being returned from HitBTC and this method of sign/burn for OMNI MAID allows time for people to eventually get their OMNI MAID returned and still be able to go through the process. Snapshot would not allow that
6 Likes
I think the main reason being there are so many omni MAID’s locked at exchanges that may or may not unlock in the future. Think about Poloniex, Cryptopia (which started paying out customers), HitBTC is also one of them. If they would go the snapshopt road, the rightful owners can not claim their maid if they would ever get custody of them again.
2 Likes
Makes sense, thanks for the clarification.
Current BTC transaction cost:
3.266 USD/tx for Jan 21 2025
Not too bad IMO.
2 Likes
On one hand, it shouldn’t be a big deal; just do it on one, then see what the TX fees are & repeat… slow, but not too tricky.
But it’s also insane that Bitcoin’s capacity is still so miniscule that fees are so high after all if the years the dev / community have had to scale it… I look forward to the day it gets overtaken due to the complacency of the Bitcoin devs and community… hopefully ANT will be the token to do that in time 
6 Likes
There is an alternative but it is more complex rather than less. It does address two of your issues:
- avoids use of OmniWallet and exposing private key to the website (which should be ok but the idea gives me the willies).
- makes it easy to set and adjust the fee, though you would still need BTC at the address
The alternative is to create and broadcast the transaction using another wallet from your own computer.
That’s complex and requires care, so not for everyone.
There’s an old post on the forum which links to a blog explaining how to do this, with Electrum I think. I don’t know if anyone here has tried it though. More willies!
2 Likes
I actually might look into the OmniCore desktop client (Omni Layer: Download) and automate the process. I am not sure though yet as it’s a tradeoff of my time (and potential risk from my bad coding skills). Should I eventually do some automation, I will post it here so that others can use it too (should there be other individuals who made the stupid decision like me to split the stash into a myriad of paper wallets).
1 Like
Is there any chance that this process, if paired with a catastrophic network failure, could lead to our OMNI MAID tokens being permanently lost?
I believe from previous discussions in stages there will be a clear record in the blockchain of the amount burned, thus all that would be needed is either re-executing the transfer with the restarted network.
But while the network is using ERC20 then your tokens will not be lost and they just restart the network and you have your tokens. Maybe if too many payments have been made then they restart with the tokens you exchanged and a new contract.
SO a couple of options, but the record of what was exchanged is on the blockchain, no matter how they restart the network
3 Likes