I used to think that electronic signatures were a complete solution. Click, sign, a green checkmark appears—everything is done. Valid, secure. Like most people, I never really questioned it. It seemed that as long as it was produced by a large platform, the underlying laws and structures must be solid.
But over time, this idea began to feel... incomplete.
It’s not entirely wrong, just a bit naive.
Because once you step out of the controlled environment, these systems don’t flow as smoothly. Laws are not unified, there’s a lack of mutual trust between jurisdictions, and data does not flow as freely as the interface suggests. When a seemingly simple signature fails across systems or borders, it exposes a deeper issue: these systems are effective within their own environment, but once they need to interact with external systems, fractures occur.
This also changed the way I look at problems.
I no longer just focus on the act of 'signing' itself, but I start thinking about what happens after. Because a signature is not the endpoint, but the beginning of a dependency. The truly critical question is: can this proof exist long-term, be passed on, and still be valid when needed in the future?
When I started to understand the Sign Protocol, I didn’t see it as an ordinary signing tool. On the surface, it seems similar. But its core logic is completely different. It does not focus on 'signing this action', but rather on 'what remains after signing'. It tries to create evidence that does not depend on a single institution, rather than entrusting some company to store and verify.
But this only makes sense under one premise—the system must not only be able to 'create', but also must allow this content to 'persist'.
It can be understood this way: traditional electronic signatures are like putting a contract in someone's office, trusting they won't lose it, won't tamper with it, and can find it when needed. Blockchain-based proof is more like putting a contract in a shared archive, controlled by no one individually, but verifiable by everyone.
Sounds powerful. But the next question is: will it be reused?
Because most system issues stem from here.
It's not in 'creation', but in 'integration'.
They generate results, but cannot flow. Like currency printed but not circulated—existing, but without function, no interaction, and unable to generate value.
So I began to look at it structurally.
First is 'interactivity'. A system only makes sense when participants can collaborate smoothly. If users, developers, and institutions can create and verify without barriers, then the system can truly form. Otherwise, it remains fragile and limited.
Secondly is 'reusability'. This is where value truly begins to accumulate. If a proof generated in one scenario can be used in another, it is no longer a one-time result but becomes a building block. Value begins to stack from there.
Then there’s the 'network effect'. Not conceptually, but actually happening. When every new participant can enhance the value of existing data—through verification, citation, building—the system will naturally grow. If every use starts from scratch, then accumulation cannot form.
So, what stage is such a system currently in?
It has indeed been applied in different regions. This indicates that it is advancing. But 'existence' does not equal 'integration'. A system being used occasionally does not mean it is relied upon daily. True infrastructure becomes gradually 'unnoticed'—not needing special attention but always running.
From a market perspective, it is well-positioned at the intersection of identity, ownership, and law. But it is still growing. Current activities are more project or collaboration-driven rather than sustained natural usage. Engagement is increasing, but still relatively concentrated.
This raises a key question:
Are people 'needing' this system, or are they being 'guided' to use it?
The two are completely different.
Incentives can bring activity, but cannot bring sustainability. True strength comes from repeated use—people return again and again because it solves long-term problems. If a proof is created once but never used again, then the system is static. But if it is repeatedly referenced, validated, and built upon, then the system will begin to maintain itself.
There’s a deeper question.
If such systems are widely adopted, especially at the government level, they bring not only efficiency but also 'permanence'. Records exist not just in the moment but exist long-term. This is not just a change at the tool level but involves issues of control and boundaries. Technology does not determine use, but it expands possibilities.
So now, my perspective on these systems has changed.
What truly gives me confidence is not the publication or promotion, but the usage patterns. It makes sense if I start seeing these proofs flow between different independent systems. If institutions rely on it in their daily operations, that's even further. If developers build based on existing data rather than starting from scratch every time, that's real growth.
But if the activities are intermittent, incentive-dependent... if the results are not reused... if participation is still limited...
That indicates this system is just 'creating' and not 'flowing'.
And I am always thinking about a core point:
The truly important systems are not those that 'create something'.
But those that keep these things flowing—being used, being referenced, being integrated into daily operations.
At that moment, it was no longer just an idea.
It has become infrastructure.
@MidnightNetwork #night $NIGHT
