BTC generally has large fluctuations on weekends.

Let's see if we can recover the drop of the past two days #BTC .

Weekends are more suitable for researching hidden altcoins.

I have recently been studying the Schema mechanism of $SIGN , and after researching it, I have a strange feeling that the more I look at it, the more I feel that there is a question hidden behind this design choice that the SIGN team may not have publicly answered yet.

What is Schema? In simple terms, it is a template that defines which fields can be included in an Attestation, what type each field is, and how it is read. For example, for a degree verification Attestation, the Schema defines that it contains fields such as school name, degree type, and graduation year.

@SignOfficial allows anyone to create their own Schema; this design is open and flexible, theoretically capable of meeting the credential needs of any scenario.

But when I sat down to think seriously about it, I realized that this flexibility comes at a cost.

If University A uses one Schema to issue degree Attestations, and University B uses another slightly different Schema, then to simultaneously verify the degrees from both universities, applications need to support both Schemas and adapt to both sets of field logic. The more types of Schemas there are, the higher the development cost for applications that want to read and verify these Attestations. #Sign地缘政治基建

Openness brings flexibility, flexibility leads to fragmentation, and fragmentation harms interoperability. This cycle is a real tension in the Schema design of the Sign Protocol. Whether SIGN has figured out how to solve it is what I want to know the most right now.