Re: DNotes 2.0 - Bridging the Gap Between the Centralized and Decentralized World

Brief(ish) development update
[...]
Automated Invoicing
The current market solution to invoicing is to generate unique crypto addresses for each new user or invoice, meaning incoming payments aren't sent to a single receive address. Our solution bypasses this limitation and will allow users to utilize invoices directly without any additional burden to the consumer, allowing for full integration into existing payment gateways and financial systems.
[...]

Great info Tim. Automated Invoicing is a key factor here, with further recognition in the future, as day by day traders don't care about that.

I also watch Stratis closely and they are way ahead of its competition. Stratis Breeze Node is their key advantage, along with other newly developed features. Privacy transactions are a MUST for a coin to succeed in crypto space.From what I'm seeing, DNotes is following Stratis path along with some unique features as you mentioned above. From my point of view, DNotes has a great potential here, most depending on your core development team skills. From a simple investor view, I would buy DNotes over Stratis for one simple reason: higher PoS reward.

This all looks like everything is on track and very much heading in the right direction. I had some idea about most if it, but the Automated Invoicing both interested and confused me.

I think I understand about providing a single unique address for receiving payments. But I don't understand how the current market solution to generate unique addresses to accept payments is anything other than a choice. I don't know how or why it would be enforced by a cryptocurrency.

My guess is my knowledge gap here is then what leads me into not understanding the 'automated' part of the invoicing process. Huh

Let's say you are a business and want to accept cryptocurrency payments, you currently have two options:
1) Run your own server with a hot wallet connected to your website, and for each transaction tell the daemon to generate a new address to accept payment, the new address acts as an invoice number. Of course, in order to do this you need a good amount of technical knowledge, custom integration as a payment solution, and as a result in house support processing and handling.
2) Pay a company a fee to accept the cryptocurrency for you.
Neither of these options make it easy to take full advantage of the strengths of cryptocurrency. With what we have developed you have a system that can automatically invoice the transaction, integrate with blockchain and cart/payment systems, automatically verify and confirm the transaction was paid, and all with very little technical knowledge and less than 5 minutes setup time with your existing IT staff. I can see where the automated part can be confusing, from the perspective of solely a cryptocurrency / blockchain solution.

Here is one of hundreds of applications. TimMarsh, you are really good at research and evaluation. Let's say you were interested in researching cryptocurrencies and providing your analysis on them. You know there is a limited market for this information and ad revenue from a website or youtube wouldn't make it worth your while. You also know that people may pay but may not want to pay a lot of money for this report and analysis, but if you could charge them a small amount, let's say 0.25 cents, they would be happy to buy access to this report. You can't accept 0.25 cents and expect to actually receive 0.25 cents, that is even if you can accept 0.25 payments. Using cryptocurrency is either too complicated, or a manual process to accept payments. But imagine if you had a wordpress blog, installed a plugin, and could automatically accept and confirm payments, automatically deliver the report once confirmed, and get the full 0.25 cents, in cryptocurrency. What we are releasing is the base for this kind of system, completely secure if you need it to be, easy to use and understand.

Thanks for taking the time to explain so clearly, but the fog is only lifting slowly for me.

So it is already possible for me to do some work for someone, and when it is done, send them my DNotes address and ask them to pay into it. If I'm not expecting many payments, and they are all of different values, I could spend the time working out who payed what. So accepting 0.25 cents is already possible.

Creating a new address and giving it to only one customer has the advantage that I can match that address number with the customer and prove I have been paid. So the unique number doesn't allow payment, it enables attribution.

But the payer can always provide their pay-from address in a remittance advice which will enable attribution. And if I wanted to automate, I suppose I could ask them to email me their from address, and then use ITTT to search the blockchain for a payment from that address, to my address, after the email date until it finds it in a block that is at least two links old. Then have ITTT email them the article. That would be automated, but a bit of mucking around.

But DNotes2.0 will enable automatic event triggers that occur after a transaction has been processed?

This all sounds really interesting, especially if people can set it up themselves. The paid v.s. ad-sponsored mobile application market has indicated people are willing to pay a small price rather than see advertising. And the Youtube model of paying creators with advertising revenue is skating along a cliff edge as advertisers withdraw contracts due to mildly controversial content. So the market is clearly hungry for a micro-payment solution that is secure and easy to implement.

Personally, I'd like to see a browser plugin that recognises pressing a micro-payment button, and pops up an approval pane. I can mouse click a 4 digit pin on a randomized-position keypad to approve amounts less than a dollar. You do know your work will never end, don't you?