You mean what was left after the service fees had been deducted? 
2 Likes
I’m very interested in knowing how you think we can solve this issue, I also hesitate a lot before sending a crypto tx. In the banking system it also sometimes happens to me, e.g. when you need to enter a bank code like SWIFT / BIC / CBU in my country, etc.
I was thinking that the proposal about having a standardised public profile (with its public ID chosen by the user) which contains wallet/pk addresses could solve this issue since people would just need the public ID of the recipient.
Do you have any other ideas/thoughts?
I think if we solved this issue with SAFEnet/safecoin it would be a big advantage or differentiator over other crypto-coins for average people.
9 Likes
This sounds similar to Dash’s plan for Evolution Dash - Dash is Digital Cash You Can Spend Anywhere sending to names not complicated alphanumeric strings - that can’t come soon enough for me!!
5 Likes
I think just having everything complicated under the hood, just like self encryption and everything else is the biggest thing. The thing that intimidates most of us is these long strings of random numbers! How do I know for sure the cold storage priv key is right if I don’t want it to touch the Internet?? Well being that the Safe Network is secure is a good start, then if people don’t have to see long strings of numbers but instead just balances, contacts/friends, bill payment, send and request funds buttons, then I think people will feel comfortable. Maybe even notifications that who is supposed to receive funds could confirm would be even more reassuring.
4 Likes
Yes, I also like the idea of being able to send a payment request, e.g. if you borrow money from a friend he can send you a payment request/friendly reminder at the same time, and your wallet app can show it to you in a list of debts or something like it.
6 Likes
Yes exactly! I actually like the term “friendly request” even more! Haha I’m being totally serious btw
3 Likes
Well…there you go another extra item in my personal roadmap…you know for which app, don’t you? 
4 Likes
Be great to have a google hangout alternative. Is there one on offer yet? Think Maid is the most moral project in crypto. Knew that when David and Nick didn’t take the piss when I bought them lunch at Scotts, and insisted they get back to work after 45mins of grazing.
Bought a few BTC worth of MAID on that alone.
But enough blowing smoke. A hangout hosted locally be the business.
1 Like
Basically I’m scared that I screw something up because I’m distracted, or theres some other small mistake that I didn’t see and now either
- The coins are sent to the wrong address or one that doesn’t even exist (one missing character, for example),
- The wallet is broken and all is lost,
- Something went wrong with a change of passwords and now I don’t have access anymore
I had a look at Dash Evolution and that certainly seems to solve some issues. For instance, it’s hard to know if the address youre sending something to is the correct one. You always have to compare beginning and ending, or something like that.
Being able to chose from a drop-down list of names would help a lot. You wanna sent to Polo? Chose “My Poloniex account” from the menu.
Also if you enter an address, it should look an entry in the database up and tell you wether you have already sent something there and the nickname (“My Poloniex…”).
Something I would love to have for all “my” addresses, wether I control them or not (like my polo address), is the ability to “pre-send” a tiny fractionor maybe just an information, and immediately get a response that everything is set up correctly. Kinda like a Simulation.
Maybe this could be the “friendly request”, just the other way around. I’m sending somone or myself the information about my intended transfer, and the other person (or myself) can respond by clicking on “everything okay, send” or “wrong, abort”. Or something like that.
Hope that helps
3 Likes
Those are very nice ideas, it sounds like having a tiny communication protocol for transactions is what we are all saying here.
I’m thinking that it could be even automated, i.e. you send a “friendly confirmation” request, the other party replies with “yup, this is me and the amount is correct”, and your app automatically executes the transaction upon receiving the confirmation (well, or ask you with a single button popup for final confirmation).
However all this will need some sort of signature verification to avoid that someone else than the intended recipient received the “friendly confirmation” (due to incorrectly typing the recipient’s address) and reply with a more eloquent response like “oohhhhh yeahh…sure, this is me and the amount is more than I was actually expecting” 
4 Likes
I love the idea of a pre-send! I would definitely use that feature
3 Likes
Maybe that can be in the wallet database, because the receiving end usually will not have an APP running that can respond. So in the wallet DB there is an area for expected payments to that wallet, and that would consist of a friendly name for the receiver, the friendly name of the sender and the amount. The data is encoded with the friendly name of the sender (or ID of sender) so that crawlers cannot see the info.
So your APP being run by the sender reads the receiving wallet’s DB and the only thing it can decode is this “message” with friendly names and amounts.
1 Like
…perhaps simply with the public key of the recipient, similar to how you do when sending an email. So the protocol is just an exchange of emails/messages with perhaps a tx ref id.
Cannot be the recipient because that is what the crawler is reading the recipient’s wallet so the crawler knows that public ID. No it has to be the senders ID (or friendly name or some other code of the sender)
The idea is to reduce mail traffic, This way its in the receiver’s wallet’s DB, a static value and can be read anytime by the sender until the receiver removes it. Ideally the recipient’s wallet APP would remove the message when it confirms the receipt of the coins.
People can loose email, ignore emails etc so why not simply embed the message at the source, less hoops to jump through, less places of failure.
- Sender has purchased from or agreed to pay the recipient.
- The recipient’s places the “info” into their wallet (via an APP)
- The sender enters the recipient’s info in to the send funds part of the wallet APP
- The wallet APP reads the recipient’s wallet’s DB and displays the info/message
- The sender confirms/rejects the transaction before any coins are sent.
I was describing the case the sender triggers the flow with the receiver without even knowing about it, so the receiver would find it out when opening the app as the request will be in his/her “friendly confirmation inbox”.
You seem to be describing the use case when the receiver starts the flow and the sender is aware of it.
Yes. Otherwise how does the receiver get the chance to put in a personalised message for the sender?
So if the sender is initiating the send to a receiver unsolicited, then in that case the receiver wallet’s DB could have a friendly name for all to see stored in its wallet’s DB,
The problem with this is that a scammer could have the same friendly name and pretend to be that person/wallet/ID.
The scammer maybe known to both or one of the sender/receiver and send a crafted message telling the sender the receiver has changed wallet ID’s.
The idea of the sender sending without the receiver asking for the funds is going to have these problems.
NOW if the sender has a list of “favorite wallet ID’s” that they have sent funds to before then the sender could associate friendly names to those addresses and this would be stored in the sender’s wallet DB
1 Like
You are clearly a lot smarter than me so this may well be dumb but is it
not possible to sign a transaction in (maid)safecoin the way you could with
something like a btc transaction? Perhaps with the receiver signing with a
hash of their wallet public key or of a concatenation of both sender
/recipient public keys? Or is that stupidly insecure / otherwise
unworkable?
I love mathematics - now I just wish I understood it too 
1 Like
@Meth, I was thinking along those lines too. This is what I understand, in the scenario that @rand_om was proposing to solve:
We can send such a “recipient confirmation request” message using the recipient’s public ID (similar to the email public ID), to the recipient’s inbox, and expect the receiver to reply with a signed message, i.e. the sender will then check that the response was signed with the signing key associated to the recipient (the recipient’s signing key could be also published in the public profile associated to the recipient’s public ID).
However, if the sender enters an incorrect but existing public ID (i.e. another recipient’s public ID) then you could get a valid confirmation flow but the recipient is not the intended one. Or in the case that @neo is pointing out that a scammer convinces the sender that the public ID changed, you then end up in the same situation. So there seems to be a need of a previous agreement (or awareness of a tx request) between the sender and receiver.
The option of having a contact list is obviously a good enough solution, we just need the app to provide you with a good way of adding addresses to it, like a post-transaction step where it offers you to store the address involved in the recent tx in your contact list with a friendly name, just like some of the home banking systems offer today.
1 Like
I imported my private key from Blockchain.info into Omni wallet. I assumed my same btc address that maidsafe are attached to would show up. It didn’t. Used Omniexplorer.info to check. Still have the maidsafe, but not showing up in Omni. Any ideas?
Sometimes the display of what coins are at that address doesn’t work. The information is gathered using your browser (afaik) and sometimes doesn’t work.
Does the public address show up in your wallet?
Try entering the public address into omniwallet.org using the check balance page without logging into your wallet and see if that is working