The case for a way back.

The problem

When you support family across borders, the last step matters. A balance on a screen does little to explain why a payout is delayed. A lost phone can turn a routine payment into a recovery problem. A statement that an asset is backed can still leave the holder unsure about who has a claim and how redemption works.

Auvellum’s starting point is that people should be able to rehearse recovery and understand the route their money would take before they depend on either. Families are our starting audience. Wallet users, banks, remittance providers and payment teams bring a different perspective on where the experience breaks down.

The product design

Access you can rehearse

We intend people to use a wallet they control and to practise recovering it on a replacement device using the wallet’s own process. The exercise should be understandable without Auvellum online. Recovering a wallet can restore control of its keys. Access to a particular asset or a route to cash still depends on the asset, network, provider and local rules.

Asset information alongside the balance

We plan to show reserve and transfer holdings separately. For each supported asset, the information a person needs includes the issuer, applicable fees and restrictions, and who can redeem. Where backing is relevant, we would identify its source, who holds it, when the supporting evidence was published and what that evidence covers.

Confirmation through to receipt

Before a person decides, a useful quote should show the total cost, any exchange-rate spread and what the recipient is expected to receive. A transaction recorded on a network and a completed cash payout are distinct events. The service would show both, including what a delay means and which party can help.

How the business would earn

Our proposed business model is software licensing and integration services for organisations that need clearer records and better support for their customers. An institution should be able to assess that value through fewer unresolved cases, more successful recoveries and less time spent finding out what happened to a payment.

Company financing and operating costs would be kept separate from any customer assets. Any fees or commercial relationships that affect the user’s cost or choice of provider should be disclosed before use.

Where things can go wrong

Loss of wallet access

Lost or stolen recovery credentials can lead to permanent loss. A recovery exercise helps people check their backup while they still have access.

Asset value, backing and redemption

Digital assets can lose value or become difficult to sell. An issuer may impose freezes or limit redemption. The documents for a supported asset should explain who has rights, how they can exercise them and what happens if a counterparty fails.

Network, provider and payout failures

Transfers can be delayed, rejected or irreversible. A second provider may depend on the same underlying services as the first. A viable alternative requires evidence that it works under the conditions it is meant to cover.

Local rules and customer eligibility

Requirements can differ by country, provider and activity. Availability, verification and limits would be disclosed for each market before any applicable release.

Responsibility and review

Auvellum intends to publish who is responsible at each handoff, including which party handles wallet support, asset queries, settlement and complaints. We plan to commission independent security review before any release involving real assets and publish its scope, material findings and limits when disclosure is safe.

We want to hear where people get stuck. Community feedback and security reports can help us find weak assumptions and improve the experience. We’ll explain material changes through dated public updates. Report a security issue or suspected impersonation.

Release criteria

The public roadmap describes the work to be evidenced. Release decisions depend on the relevant product, security, legal and operating conditions.

• Demonstrate that users can recover access independently on a replacement device and understand their responsibilities.
• Verify the applicable contracts and permissions for each activity and market. Publish eligibility, fees, custody and complaint routes in plain language.
• Test the full journey from a quote to a received payout, including delays and exceptions. Check an alternative route where it is feasible.
• Complete independent security review for the intended release and document material findings, actions and residual risks before offering live use.

About this paper

Auvellum is in development. Beta release coming soon. This is a description of the proposed software project. It contains no offer to buy a cryptoasset or invest in the company.

Further reading

• World Bank methodology for comparing remittance costs
• Ethereum.org guide to wallet security and scam prevention

StartMadeSimple Ltd publishes this paper on Auvellum.com. See the company details and website terms. For a question about this paper, contact the founder.