Umm, why don't you store the invoice data on the blockchain? You can encrypt it with memo keys so it won't be public.
You are viewing a single comment's thread from:
Umm, why don't you store the invoice data on the blockchain? You can encrypt it with memo keys so it won't be public.
First version did store it on the blockchain, but I was worried for large invoices that there was the possibility you'd hit the size limit. But it's a good feature request to store it on the chain encrypted with memo keys for smaller invoices. Thinking about it, some invoices might only have one item.
I started thinking about this more and realised they could be encrypted posts. I was in a custom JSON mindset around this. I'm pivoting to just use Hive directly and keeping SQLite as the cache.
Okay, it uses encrypted posts for the invoices now which works for larger invoices.
For large invoices you can use some kind of chunking. Half of the items go in one transaction the other half in another, and they share the invoice number plus an ordering.
Or you can attach the pdf which is stored on ipfs or similar.