Liquid · The work after the theft
After the theft, one builder stays on Liquid
OceanSlim argues that the contract designs can outlast the chain they run on. Elsewhere in the same reading, users are still asking how to get their money out.
OceanSlim has spent the past year building on Liquid and is not leaving after the September 6 theft. The argument in a new essay is about what can be built there, and what would remain useful if the sidechain itself failed.
The author describes anchor, an automated exchange whose pools are controlled by rules governing how their coins may be spent. In OceanSlim’s account, it has no administrator key or upgrade path. That work led to a Jan3 contract for a further prototype, still private.
The essay acknowledges the federation and the peg as trust assumptions. It calls for more scrutiny of Elements and a better release process, while arguing that the exploit did not invalidate the contract designs. The distinction is between losing a place to run the work and losing what the work taught its builder.
OceanSlim hopes to carry those designs to Bitcoin if it gains the needed capabilities, or to another experiment if it does not. The line that holds the argument together is The code is transitory. The understanding isn't.
It is a case for continuing research, rather than a claim that the chain has become risk-free.
The user’s question remains more immediate. Tico reports intermittent access through Aqua: Sometimes Aqua enables peg-outs, but mostly not working
. The report concerns access through that wallet, and illustrates why a chain processing transactions is only part of the recovery.
Leito is looking for an alternative: Is there an OTC trading desk for L-BTC?
The two conversations belong beside each other. The developer wants the work to survive. The holder wants a usable exit. Continuing to build answers one concern; it does not settle the other.
