TAP-10 v1.1：链上数据需双运营者一致，无多数投票TAP-10 v1.1: On-Chain Data Needs Two Matching Operators, No Majority Vote

TAP-10 turns every Container into both a website and a messaging endpoint TAP-10 is the DeWEB standard, split into an access layer and a messaging layer The access layer is tape://, which finds the site, reads the files back and checks them byte by byte On BNB Chain a name looks like 4246.0.tape O

When you open a DeWEB site, the client checks first and displays second TAP-10 sets a few rules for clients Answers from multiple independent nodes must agree, any disagreement means rejection Every file's length and Hash must match what is registered On Chain Each site has its own origin, and scr

Nothing On Chain can be deleted, but whether it gets shown is up to the client TAP-10 requires every client to support a blocklist Block by Container address or On Chain name, and a match won't be displayed The list is checked on every resolution, even cached ones Official clients should also offe

TAP-10 sets a strict bar for calling a site 100% On Chain The page can't reference any off chain resource, http, https, outside fonts or images all count It can't make any off chain request while running And the client has to be able to see every kind of request the site could make A client that c

There's a rule in TAP-10 v1.1 that's easy to miss When reading On Chain data, at least two independent operators have to return the same result before it's used Any disagreement means it's rejected outright No majority vote It's still a draft, but this rule is clear, better to not open at all than