Storing fuel deliveries is trivial. Any database does it. The difficulty is not storage, it is who is trusted to hold the copy. A database has an administrator, and that administrator can change a row while everyone else has to accept that they did not. Inside one company that is normal. Inside a corridor consortium, where the partners have no shared parent, it is the whole problem.
VesselChain runs on Ignis, a child chain of Ardor, built by Jelurida. It was chosen for two reasons that matter here: entries are written once and cannot be altered afterwards, and no participant holds a privileged copy. That includes us. A shared ledger does not answer the question of who to trust. It removes the question.
The delivery record: grade, quantity, supplier, date and place, and the signature of the accredited verifier who reviewed it. Written once, at the point of delivery.
Prices, contracts and commercial terms stay out of the record. What a corridor partner needs to verify is what was delivered, not what it cost.
VesselChain has no coin, no token and nothing to buy or hold. Ignis is used as a shared register, not as a currency. If you were expecting a crypto product, this is not one.
The ledger proves that an entry has not been altered since it was signed. Whether the fuel matched its documentation is what the accredited verifier assesses, and that is a human judgement the regulation already requires.
There is no administrator who can quietly edit a row. The constraint applies to a port, to a charterer and to VesselChain equally. Neutrality here is a property of where the record sits, not a policy we promise to follow.
Entries export as audit-ready evidence for your own reporting. The record is not a hostage: leaving does not cost you the proof you accumulated.