You wait for the test to fail. The air in the Pinheiros office feels heavy at 6:40 PM on a Thursday. You are Rafaela. You have worked here for three weeks. The office is in São Paulo. The office has glass walls. You can see the traffic on Rua dos Pinheiros. The traffic does not move. The test does not move.

You are looking at a function. The function is called redeemLiquid. You need to change one line in the function. You need to change the withdrawal delay.

The code is not your code. The code belongs to a developer who is gone. The developer is named Thiago. You run git blame on the function. Every line says Thiago. Thiago left the company eight months ago. Thiago moved to Lisbon. No one has his number. No one has his email.

The commit message for the function is short. The message says “fix edge case, see thread.” You look for the thread. The thread is in a Slack channel. The channel is archived. You do not have access to the archive. You look for the documentation. The documentation is on a Notion page. You click the link to the Notion page. The page says you do not have access.

The Unspoken Ritual

The tech lead sits two desks away. The tech lead is named Marcos. Marcos does not look up from his screen. Marcos says do not change the order of the calls. Marcos says the calls worked before. You ask Marcos why the calls work. Marcos does not answer. Marcos does not know why the calls work. Marcos only knows that the calls worked for Thiago.

You are living in the house. You are trying to move a wall. You are afraid the roof will fall. Staking is not like other code. Staking involves money. Staking involves time. Staking involves a liquid token. The liquid token has rules. The rules are in the code.

The rules are also in the head of the developer who left for Lisbon. When the developer left, the rules stayed in the code, but the reason for the rules disappeared.

The Developer Who Stayed

I read my old text messages last night. I found messages from 2019. I was working on a bridge. I told a friend that I finally understood the lock mechanism. I wrote three paragraphs about why we used a specific salt for the hash.

I looked at that same code last month. I did not recognize the salt. I did not recognize the reason. I am the developer who stayed, and I still became the ghost. We think we are building systems. We are actually building puzzles for our future selves. We are leaving traps. The traps are made of hardcoded integers and unexplained delays.

The liquid staking withdrawal process is a sequence of events. The user requests a withdrawal. The protocol burns the liquid token. The protocol unlocks the underlying asset. The asset sits in a buffer. The user waits for an epoch to end. The user claims the asset.

This sounds simple. It is not simple. There are edge cases. There are slashing events. There are validator exits. Thiago knew these things. Thiago wrote the redeemLiquid function to handle these things. But Thiago did not write down why he handled them that way. He only wrote the code.

The Tragedy of the Knowledge Pool

Organizations believe that knowledge lives in the codebase. This is a mistake. The codebase is a record of decisions. The codebase is not a record of the reasons for those decisions. The knowledge lives in a shared pool. The pool is unowned.

The pool contains Slack threads. The pool contains whiteboard drawings. The pool contains the memory of one person. Every engineer draws from the pool. Every engineer takes a shortcut. No one puts knowledge back into the pool. Writing an explanation takes time. Reading an explanation takes time. Shipping a feature takes priority.

You are grazing on a pasture. The grass is getting short. No one is planting new grass. Soon there will be no grass. There will only be dirt and hardcoded delays.

“

“Interpretation is not about the words; interpretation is about the silence between the words.”

– Maria G.H., Court Interpreter

In a courtroom, the silence tells you if a witness is lying. In a codebase, the silence tells you where the technical debt is buried. The silence is the space where Thiago’s explanation should be. The silence is the 404 on the Notion page. The silence is Marcos telling you to just not touch the order of the calls.

When you build on a protocol you do not understand, you are running an experiment. It is a quiet experiment. It is an experiment in collective memory. You are betting that the system will not break before you leave the company.

You are betting that you will not be the one holding the pager when the hardcoded delay causes a liquidity crisis. Staking integrations make this experiment expensive. The stakes are high. The assets are locked. The users are waiting.

You type “how does liquid staking withdrawal actually work” into a search engine. You find academic papers. You find marketing blogs. You do not find the reason for the line of code in front of you. You are looking for a foundation. You need a foundation that is transparent. You need a foundation that does not require a ghost to explain it.

The Oil in the Gears

The industry builds black boxes. We wrap the boxes in beautiful interfaces. We call the boxes “liquid.” We forget that the box contains a mechanism. The mechanism has gears. The gears need oil.

The oil is the documentation. Most teams skip the oil. They want to ship the box. They want the metrics to go up. They want the total value locked to increase. They do not want to spend three days explaining the withdrawal buffer.

A developer portal should be more than a list of endpoints. It should be a map of the mechanism. It should be a place where the reasons are as clear as the calls. When a protocol provides clear documentation, it is making a commitment.

You are still in the office in Pinheiros. The clock now says 7:15 PM. You look at the redeemLiquid function again. You decide not to change the line. You do not want to be the reason the roof falls.

You realize that you are now part of the silence. You will leave this function exactly as it is. You will pass the ghost to the next person.

We measure what we ship. We never measure what we explain. We reward the engineer who finishes the ticket. We do not reward the engineer who spends a day writing a wiki page. We create a culture of shortcuts.

We create a culture of shortcuts because we are in a hurry. We are in a hurry to reach the future. But the future is just another office where a new developer will look at our code and wonder why we did what we did.

The Withdrawal Ritual

The withdrawal delay is not just a number. It is a safety margin. It is a protection against front-running. It is a buffer for validator cycles. If you do not know which one it is, you cannot safely change it. You are trapped by the code.

The code is supposed to serve you. Instead, you are serving the code. You are maintaining a ritual. You are performing the calls in the order Thiago performed them. You are a priest in a temple of forgotten logic.

I want to build things that can be understood by people who have never met me. I want to leave a trail that is easy to follow. I want to refill the well. This is hard work. It is the hardest work in engineering. It is harder than writing a smart contract. It is harder than optimizing a gas fee. It is the work of being honest about what we know and what we do not know.

Marcos stands up. He puts on his jacket. He says he is going home. He tells you to have a good night. He tells you not to worry about the function. He says it has worked for a year.

He says a year is a long time in this industry. He is right. A year is long enough for everyone who knew the truth to move to a different country. A year is long enough for the truth to become a legend.

The withdrawal delay is the only thread left in a well that has gone dry.

You close your laptop. You walk out of the glass office. You walk into the Pinheiros air. The traffic is still there. The cars are moving slowly. They are following the cars in front of them. No one knows where the first car is going.

They just know that the order of the cars has worked so far. You are one of the cars. You are following the order. You are hoping that someone, somewhere, knows the way. But as you walk toward the metro, you suspect that everyone is just looking at the car in front of them and hoping for the best.