Graypaper for Byteball DocBot

I have a proposal for Byteball app/bot to manage multiparty documentation for various purposes.

Most simple use case can be an invoice with 2 parties involved. More complex scenario is transportation documents documents like Bill of Lading, which can involve 4-5 parties with different signing and using roles.

A typical ship freight operation involves much paperwork. Every shipment is supported by a document known as Bill of Lading (BL). This is in most part printed, signed and mailed in multiple copies. Physical document itself is a proof of ownerhsip of cargo etc, and is very important in ecrow , insurance and other other parts of logistic chain. Every container shipped is supported by this paper work.
A typical timber shipping operation can have hundreds(!) of BLs manually signed by vessel owner agents, and delivered to multiple parties by electronic and conventional means.

Here is nice introduction

Basically it is a data object with defined fields, roles, users, workflow etc. Operation may not include any payments (except optional fee forwards) although optionally there is no problem to add payments.

App/bot could be designed to handle various documents and scenarios as a chain of transactions like
issuing, editing, signing, delivery confirmations. It is easy to do receipt confirmations with signatures to prove that you have received document etc.

I have no idea if data itself can be handled onchain or offchain, but it is not much data, so in some cases it can be stored onchain encrypted etc. Data can include html markup so basically it is usable in any scenario.

Transaction would be a typical payment message with specific payload. Issuing party would input some Bytes to cover expenses for a receiving party to make a transaction so invoice receiver does need to have funds which will help adoption.

Bot/app can charge issuer some fee for the operation paid to some contract.

It would not be a problem to make ICO to fund the project and pay the fees from operation back to the contract.

There may be many other use cases like any ticketing(!)

It will not be easy to break existing workfow, but is the solution is effective and provides real paperless solution then i can see this adopted by industry. I am working with several fleet owner companies on IT projects and they can provide all necessary assistance.