Just sent you a MobileCoin!
@ruben: Whatâs funny is that, because of the design of the MobileCoin system, which is so focused on privacy, you wonât have any idea who sent you a payment unless they identify themselves to you as the owner of that payment.
1 Like
77VS11jiyrn6r8gPysY3YXoEXjyxqKYvrVcZrKqZ8UZqhgd7VQouXJjBNdXsp6MFYWjXmag4iZMzihtBwqZn8a11qh7XfnrMovUExy2DXWki6ZHiyfpF38i
Just sended you 1 mob!
5mNKccvLY19SQzASyjmg1qdjdvdQz8HBZmyM7fuBa8czQmUE4cAa8X531GkTnQ48R98SsYzaEEnbcnB4hg8Zu7nAqfbXhDasqvFnr1FYsjkUzqCv2wvA4FiewrRYsa
4mbUJhG8p6ScTauPKG78k66si2avpgiiccuNRNPm3VUqnW9Y3YokgFpUf5FafzAFDFctUfn1qDA2g5rsj2LdUkNHsJe7C2hzM3rHDm26fzzSyaqJW4pQGCmC9sN
86vmNVUv2oER3whCqvH2fvsMA8VQycHqfqqfsPQYhFQvbJuj7mVLUNqGD3SJ4RBTFztSAgVhQKcCA9DHDndC5dHPiURtbpgd2wHD6HgkHitx3T8QHwQbx6gpa6i2YMtQfcYgrYyuR8bExBLJoVZGXnD4o9c6Eu6F3ZHvu3KMMFJd8hj3uhDfmq9Gtx
Thanks 
I just fulfilled this request which was for 0 MobileCoins. Itâs interesting that you can send 0, right? As a protocol, MobileCoin never has any idea what the amount is in a transaction, only that it exists in a range of possible values (I think itâs 0 to 2^64 but Iâll have to check with engineering). This is called a âRange Checkâ. The nodes donât check that a user is sending 5 MobileCoins or 100 MobileCoins or whatever amount youâre trying to send, the nodes check a mathematical proof that the amount youâre sending is within the acceptable limits of the system.
This is one of the ways MobileCoin protects your privacy. MobileCoin nodes have zero knowledge of the values a user is transacting.
2 Likes
Just send you some MobileCoin!
1 Like
Received 
!
1 Like
b2xgzbp5RUEfPXs39qfybjemLBDNmKKVN9r2fYruV5gyoPXk9U6iPGZrbypYJqDhbeM8YBS32Y62HvqRdCePqvnZG9vcDktX84LTfTFfjm7E1oPx6hMuHQeCvW1
Just fulfilled your request!
Interesting (and novel!).
I came at it with the idea that it would work âjust like my [insert name of other consumer payment brand]â. However, the privacy angle means, I need to readjust my understanding of how it could work.
Use case : Anonymous Tip Jar â If I wanted a âtip jarâ I would just publish a payment request and have people push as much MOB to it as they would like.
Use case: Paying a vendorâs Invoice â The Vendor sent to me a unique Request for Payment for the amount. â The transaction is anonymous, and if the Request key is securely sent, the âpaper trailâ is on other systems.
This will open up some really novel use cases. Cool work!
1 Like
6rc7YJDHtHDLv6YB3gpEdC15QonyoVf8VMkXfjvWU3iNtgY2EbVHPS9EZdcxjwStTmYxPdrWAsmxscxxTM2MkD645eaidhvxrwk7kabFAyN1fpHEDRZUU6S3P7QoRLtCgisbKJeTLj6992mhe6AC6khCkNKHeuMVUbzF3r8
Anyone else getting a
"Unable to connect to mobilecoind on 127.0.0.1:4444.
Are you sure it is running and accepting connections?
The error was: RpcFailure: 14-UNAVAILABLE failed to connect to all addresses
Terminated"
both for the watcher node as well as the testnet client package?
What version of MacOS are you running?
same error here too. I run testnet on ubuntu 19.04
Exactly.
The vendor invoicing stuff gets to be really interesting. One of the cool features of MobileCoin is that you can create a master key and associate sub-master keys to it. In this way, a single Master key can manage nearly infinite sub-addresses, so you could give every transaction a unique subaddress to bind customers to transactions (but still get fast aggregate statistics across all of your subaddresses).
This solves the problem of how service providers who are ok knowing who all of their customers are (like exchanges) can service MobileCoin users. It does not solve the problem of how service providers who donât want to know who their customers are but still want to service MobileCoin users (think oblivious transaction recovery).
For that we need new infrastructureâŚ
Cheers,
Joshua
3 Likes
ubuntu 18.04 LTS (elementary OS 5.1)
Hey @madde - this can happen if you have multiple mobilecoind running at the same time. You might need to kill the other mobilecoind processes (something like killall -9 mobilecoind).