Crypto wallet for money transfer
I am creating a discussion where I ask you to describe or give ideas for creating a cryptocurrency wallet that will be focused exclusively on cryptocurrency transfers.
We ourselves are engaged in exchanging cryptocurrency for fiat – mainly for stablecoins (USDT and USDC), and every month one or another of our partners or clients loses funds: someone connected to a drainer, someone sent money to the wrong address, someone got scammed in some other way.
Every time I send an amount of 100,000 USDT+, I think that the money will go to the wrong address. And when transactions are over 1 million dollars at a time, I really want to split them. Every time I send about 500k, I go to Tronscan and check whether the money went to the correct address or if all the money was lost…
I want to create a wallet that will be designed exclusively for making transfers – for financial operators, for those who use cryptocurrency not to get 100X on memecoins, but for those who simply transfer money using USDC or USDT.
If you have ideas on what should be included in the wallet, I would be extremely grateful. Advice, thoughts, contacts, problems you have encountered.
Main functions I want to add to the application:
AML checks – integration with several providers and checks inside the application itself, not in separate services as it happens now. That is, inside the application you press a button, check that the client’s money is clean – you can accept the funds.
NFTs that will identify the user.
A person can generate an NFT that will be located in their wallet. A transfer can be made using this NFT and the address, like in a bank.
User 1 transfers money to User 2.
User 1 enters the wallet number and the NFT number – i.e. two numbers.
When entering, it shows that:
He has already transferred to this NFT 13 times.
This NFT – “Picture with a dragon” and the name “Equalizer”.
If the numbers do not match, the transfer does not take place – like in a bank, if the name does not correspond to the account number, the payment does not go through or is returned.
User 1, after checking that the picture, name and number are correct, makes the transfer.
In this way we reduce the error in transferring funds to zero.
The generation of an NFT for a payment should cost about 20 USD, which will not allow scammers to work, who create thousands of wallets automatically and then send cryptocurrency from similar addresses. Creating 100,000 addresses at 20 dollars each is problematic 😊.
“Anti-scam detection.” There are a lot of options and cases of how exchangers scam for hundreds of thousands of dollars. I want to create tools that will prevent getting into such situations. A small list:
“Dot” – when they send 16.239 instead of 16,239. And then ask for a refund, or the boldest take cash personally.
Fake cryptocurrency – when they send cryptocurrency identical to USDT 1 to 1, but created independently.
The most common type of fraud is the triangle. With the creation of an NFT that will identify the sender, it will be much more difficult to make triangles, for example:
The client exchanges 100,000 USD for 99,000 USDT.
The client receives a test (10 USDT) from an address to which an NFT was attached 2 days ago – everything is clear, the deal can be stopped.
Small crypto that comes after a transaction – when you send 100k+, and then you receive 10 pieces in TRX or in USDT from similar addresses to your wallet.
Connecting AI that will analyze wallets and show that something is wrong. Personally, I often understand that a wallet is “black” just by looking at the type of transactions in the blockchain. For example, if:
the wallet is new;
it has 1–2 transactions of 100–200k;
we look at the path of the crypto and see that the sources are empty wallets, and there is only one run of 500k in a single transaction – obviously this is some nonsense, and even if AML shows that everything is clean, you should be cautious.
I think AI can learn to analyze wallets and warn the user about possible danger.
Secure transfer:
User 1 makes a transfer.
A code is generated for him.
User 2, who receives the money, must enter the code that was generated for User 1 to accept the payment.
If the code is not entered, the payment is returned back within an hour.
If the code is entered incorrectly 1 time, the payment is returned back.
In this way we reduce the error in transfer to zero.
Ban on connecting to drainers.
Connecting to drainers is just a goldmine for scammers.
So many of my friends and partners lost millions of dollars on this stuff. I believe it is necessary to simply prohibit connecting the wallet to external resources – especially those that transfer keys.
Comments, labels, and documents when making a deal. Together with the payment, a message comes – like in a bank “Payment purpose”, or a document (NFT) – for what the payment was made.
If you enable this function, you will be able to send a message to the wallet owner.
When making a payment, you will be able to specify that this payment is for the purchase of a certain product or a specific service.
And you will be able to attach a document. For example, a company issued an invoice, the client paid the invoice, and attached this invoice to the payment. Basically, this is good for financial providers: if I understand that the money in the wallet is there because the person received payment for design services, then I will be much calmer working with him.
Closed transactions. As a future feature: ensure confidentiality of settlements.
By agreement, it may be possible to introduce mechanisms of enhanced transaction privacy, similar to Zcash or Monero.
Personally, it bothers me a lot that any scammer or bandit knows how much money I currently have in my wallet. I want to create a tool that would allow hiding the amount of money in the wallet. Probably, for this we will have to make our own blockchain.
I would like to hear your thoughts and ideas about which functions would be useful for users.
If you describe the problems you have encountered, that would be excellent.

Replies
It should be very nice to remedy the crypto users' pains!