{ "version": "https://jsonfeed.org/version/1.1", "title": "Revow notes and logs", "home_page_url": "https://revow.org", "feed_url": "https://revow.org/feed.json", "description": "Arguments, explanations and dated changes from an open lab on professional credentials.", "language": "en", "items": [ { "id": "https://revow.org/changelog/pass-ten", "url": "https://revow.org/changelog/pass-ten", "title": "Second verification pass: fifty-four registers, and two countries that already issued the keys", "summary": "Seven registers added across North America, Europe and Asia. The pattern that keeps repeating is a state that has already built the cryptography and still publishes no file.", "content_text": "The index now carries fifty-four registers across thirty-seven jurisdictions and forty-three trades. Seven rows were added in this pass, each checked by hand against the authority’s own published pages on 10 November 2026. The pass went deliberately wide rather than deep, because nobody knows which authority moves first and a table that only covers the places this lab already understands is not evidence of anything.\n\nTwo of the new rows are grade B and both arrived by a route worth noticing. New York publishes active real estate salespersons and brokers as a dataset on the state’s general open data portal rather than as a feature of the licensing register, in CSV, JSON and XML at fixed addresses. California publishes every licensed contractor as a free master list in three files, one of which lists the people attached to each licence rather than only the licence. In neither case did somebody persuade a regulator to build an API. A general policy applied to a state agency, and the file fell out. That is a cheaper path to tier A than any amount of arguing with a licensing board, and it is the one this lab should be pointing authorities at.\n\nThe United Kingdom supplies the clearest priced gate in the table. Anyone may search the medical register free, and the General Medical Council describes it as the only up-to-date publicly accessible database of every doctor eligible to practise in the country. The bulk file already exists in exactly the shape RVW-5 tier A asks for: the whole register daily, delta files seven days a week, CSV over SFTP. It costs eight hundred and fifteen pounds a year plus VAT, and republishing any of it requires a second licence granted only after the GMC has understood the intended use. Nothing technical is missing. A register first printed as a book in 1859 now ships a daily machine-readable diff, and what stands between it and a signed public file is a price list.\n\nThe finding that repeats, and which this lab did not expect to find twice in one pass, is a state that has already issued the keys. Germany gave every lawyer a chip card carrying a signature certificate and an identifier inside the judiciary’s electronic communication infrastructure. The national official directory is free to inspect by statute, and criminal procedure law requires courts and prosecutors to use it when appointing defence counsel, so the state has already decided this register is authoritative enough to bind a court. It publishes no file. That is the Estonian finding again, in an entirely different administration: sign the artefact, not the channel. Two independent confirmations in two passes is no longer a curiosity, it is the shape of the problem.\n\nAustria is the control for Germany. It replaced fourteen provincial trade registers with one national system in 2015, gave every trade licence a national number, wrote free public access into the trade statute so no reason need be given, and published an interface specification with version numbers. It is the best equipped grade D in the index and there is still nothing to hash. One country fixed the fragmentation and did not publish; its neighbour never fixed it and does not publish either. The professional cannot prove anything in either place.\n\nMaharashtra contributes the most honest number in the whole index. Registration is compulsory under the 2016 national statute, each of more than thirty states and territories runs its own authority and portal, and Maharashtra has registered more than fifty thousand agents in eight years while publishing that fewer than thirty-two thousand are currently active. A register publishing its own decay rate, better than a third of its entries lapsed, is the argument for RVW-6 made by the register itself. The federal split that produces this is now the commonest failure mode in the table, shared by Brazil, Spain, India and the United States.\n\nThe Philippines supplies the sentence this lab will reuse. The Real Estate Service Act already requires a practitioner to carry their registration and licence details on every document they sign, use or issue, which is the subject, the trade, the licence reference and the issuing body, mandated by law, on every piece of paper. What exists to check it against is a free search form the Commission itself warns may be delayed or wrong. Its own framing of why that matters: the card can be perfectly genuine and the registration still lapsed, because the card is not the licence, the registry is. Which is the entire argument for making the registry publishable as something a machine can keep.\n\nStill missing, and unchanged since the first pass: archived copies of the evidence with their digests published beside each row. Until that exists a row can be argued with but not checked against a frozen copy. Corrections are wanted, particularly from anyone who works inside one of these fifty-four.", "date_published": "2026-11-10T00:00:00.000Z", "tags": [ "Log" ] }, { "id": "https://revow.org/notes/already-law", "url": "https://revow.org/notes/already-law", "title": "Most of this is already law, for one trade, in twenty-seven countries", "summary": "The usual objection to RVW-5 is that no government would ever agree to it. One has, since 2006, across the whole union.", "content_text": "The objection this lab hears most is that asking authorities to publish a dated, identified, machine-readable list of who holds a licence is politically naive. It is worth knowing that the European Union decided to require almost exactly that, for statutory auditors, in a directive adopted in 2006 and operational everywhere by June 2009.\n\nRead what it actually requires. Every member state must enter approved auditors and audit firms in a public register. Each auditor and each firm must be identified by an individual number. Registration information must be stored in electronic form and be electronically accessible to the public. The register must be updated without undue delay after notification of a change. Auditors from outside the union must be flagged in the register as such rather than shown as statutory auditors. Sanctions must be disclosed publicly, and must include the possibility of withdrawing approval. The reason given in the recitals is the plainest sentence in the whole instrument: in order to protect third parties.\n\nSet beside RVW-5, that is tier A and most of tier B. A stable identifier per holder. Machine accessibility as a legal duty rather than a favour. Prompt updates. Published revocation. The only missing piece is the one this lab keeps returning to: the directive does contemplate electronic signatures, but on the information the auditor sends to the authority, not on what the authority publishes back out. The submission is signed. The register is not.\n\nItaly did something adjacent and arguably harder. Its national index of digital domiciles holds a certified electronic address for every company in the business register and every professional enrolled in an order, fed by the orders themselves, free to consult without any credential, with the code stating that consultation of those registers is not subject to authentication and that the lists are produced in open format. For an enrolled professional that address is a legal domicile, not a contact detail.\n\nSo the political argument is already won twice over, in one trade across a continent and in one country across every regulated profession. What was never asked for, in either case, is the thing that makes a published record usable by a stranger: a signature on the artefact. That is not a legislative problem. It is a key, a DNS record and a cron job, and it is the part this lab can actually help with.\n\nIf you work on audit oversight or on digital domicile policy and think this reading of either instrument is wrong, the correction is worth more to this lab than another row in the index.", "date_published": "2026-11-09T00:00:00.000Z", "tags": [ "Note" ] }, { "id": "https://revow.org/notes/expiry", "url": "https://revow.org/notes/expiry", "title": "Expiry does more work than revocation", "summary": "Revocation assumes somebody tells you. Nobody tells you.", "content_text": "Revocation lists are built on an assumption that does not survive contact with the world: that when a licence is suspended, the systems relying on it will be informed. They will not. There is no notification channel, no subscription, and usually no obligation.\n\nA claim that expires needs no such channel. It fails closed on its own, at a date fixed in advance by the person who signed it, whether or not anyone was watching. That property is worth more than a list that is only as current as its last update.\n\nThe cost falls on the professional, who has to renew. Twelve months is the cap in RVW-1 and six is encouraged, which is two signatures a year.\n\nWithdrawal still exists for the cases expiry cannot cover: a rotated key, a licence that ended early, a mistake. It is in RVW-6, and how fast it should propagate is open problem OP-7.", "date_published": "2026-11-09T00:00:00.000Z", "tags": [ "Note" ] }, { "id": "https://revow.org/notes/file-cost", "url": "https://revow.org/notes/file-cost", "title": "What a signed file actually costs", "summary": "A walk through the work of publishing tier B, step by step, with the hard part named.", "content_text": "The export already exists in some form. Licence reference, status, trade, held-by name, last changed. Pointing it at a file instead of a report is a change to a query and a destination.\n\nThe key is generated once. Any wallet or command line tool makes one, it signs the manifest and it never touches anything else. Rotating it later is a DNS change, not a migration.\n\nThe DNS record is one line at the authority domain, the same shape as the SPF and DKIM records already sitting in that zone. Nobody has to be told about it, and no registration exists anywhere.\n\nThe manifest is a dozen lines of JSON saying what the file covers, how often it changes and the digest of the current version. The scheduling is a cron job writing to the same address.\n\nThe hard part is none of these. It is the internal decision that publishing a list already available one licence at a time is allowed in bulk. That is a policy question, not an engineering one, and pretending otherwise wastes the time of the person being asked.", "date_published": "2026-11-09T00:00:00.000Z", "tags": [ "Note" ] }, { "id": "https://revow.org/notes/not-a-credential", "url": "https://revow.org/notes/not-a-credential", "title": "A licence number is not a credential", "summary": "What a register entry proves, what it does not, and why that gap decides the whole project.", "content_text": "A licence reference is public text printed on websites, email footers and contracts. Reading one proves that the number exists. Quoting one proves nothing, because quoting is free and anyone can do it.\n\nA public register closes a different gap than the one that matters here. It answers whether a licence is current and who holds it. It does not answer whether the person in front of you, or the key signing a document, is that holder.\n\nLevels 0 to 2 of the ladder all live inside that gap. They make the claim permanent, attributable and expensive to contradict. None of them binds the number to the key.\n\nOnly the body that issued the licence can close it, by recording a key against a licence and publishing the pair. That is tier C of RVW-5, it is open problem OP-1, and it is the thing that decides whether the rest of this work matters or stays a careful way of being wrong.", "date_published": "2026-11-09T00:00:00.000Z", "tags": [ "Note" ] }, { "id": "https://revow.org/notes/register-is-a-room", "url": "https://revow.org/notes/register-is-a-room", "title": "The register that counts is a room", "summary": "Three jurisdictions on three continents landed on the same architecture, and nobody seems to have noticed.", "content_text": "Checking forty registers by hand turned up a pattern that none of them would recognise in the others, because each one thinks it is a local arrangement. Ireland, Japan and Hong Kong have all arrived at the same structure: a statutory register that is authoritative and physical, and an online thing that is convenient and disclaims being it.\n\nIn Ireland the register of practising solicitors is kept under the Solicitors Act and may be inspected at the Society’s premises in Dublin during office hours. What is online is a directory whose own disclaimer says it should not be regarded as a comprehensive list of practising solicitors or of all solicitors, and that it is for information purposes only.\n\nIn Hong Kong the Estate Agents Ordinance requires a Register holding names, licence numbers and registered addresses, open for inspection free of charge at the authority’s office in Wanchai. The online Licence List says in its own words that it is not that Register, that the information should not be used for any other purpose, and that anyone wanting registered addresses or the historical periods of a licence should come to the office and search.\n\nIn Japan the broker register is inspected in person, at a counter, on weekdays, with one prefecture stating that enquiries about brokers cannot be answered by telephone or through its contact form. A national search system exists alongside it and refreshes twice a month. Digital inspection arrived in 2025, for brokers who applied after April that year, through a government business ID.\n\nThree different legal traditions, three different centuries of administrative habit, and the same answer. That is not a coincidence and it is not laziness. It is what happens when a register is designed as an instrument of a legal proceeding rather than as something a stranger consults before sending money. An inspection at a counter produces an identified visitor, a certified extract, a date and a fee. It is a chain of custody. The web page produces none of that, so lawyers quite reasonably refuse to let it carry the weight, and the disclaimer appears.\n\nThe lesson is not that these authorities are behind. It is that the disclaimer is load-bearing, and that handing out a file would not fix it on its own. What closes the gap is not convenience but provenance: an artefact that carries its own date, its own issuer and its own signature, so that a copy a stranger downloaded on Tuesday has the same standing as an extract certified at a counter. That is the entire reason RVW-5 asks for a signature rather than just an export. An unsigned CSV is another convenience that a cautious lawyer will attach a disclaimer to, and they will be right.\n\nIf you work inside one of these three and think this reading is wrong, that is exactly the correction this lab wants.", "date_published": "2026-11-09T00:00:00.000Z", "tags": [ "Note" ] }, { "id": "https://revow.org/notes/sha256", "url": "https://revow.org/notes/sha256", "title": "Why SHA-256 and not keccak", "summary": "The identifier has to be checkable by somebody who installs nothing.", "content_text": "Claims are files. The person most worth convincing is not an Ethereum developer, it is whoever inside an administration or a law firm has been handed this and asked whether it is real.\n\nThat person has a shell. They have shasum and they very likely have jq. Giving them a one line command that reproduces the identifier on their own machine is worth more than any amount of explanation, because they can check the claim without trusting the explainer.\n\nKeccak would mean a library, a package manager and a decision about whether to trust the package. For an identifier whose whole job is to be independently reproducible, that is the wrong trade.\n\nSo the document identifier is SHA-256 over the canonical bytes, and keccak stays where it belongs: EIP-712 signing and the optional anchor contract, both of which already assume an Ethereum toolchain. Mixing the two is deliberate, not an oversight. The verify page runs both halves in the browser and prints the shell equivalent beside the result.", "date_published": "2026-11-09T00:00:00.000Z", "tags": [ "Note" ] }, { "id": "https://revow.org/notes/wallet-per-job", "url": "https://revow.org/notes/wallet-per-job", "title": "A wallet per job has to stay free", "summary": "Fresh addresses are normal practice. A protocol that punishes them will not be used.", "content_text": "Agents, brokers and firms use a different address per transaction for ordinary reasons: bookkeeping, separation of client money, and not publishing a running total of their business to anyone who looks.\n\nAny design that attaches a credential to an address taxes that habit. The fresh address has no history, no binding and no licence evidence, so the careful professional looks exactly like the impersonator.\n\nAttaching the credential to an identity key instead removes the tax. The identity signs a delegation naming the operational address, with a scope and an expiry, and the evidence stays where it accumulated. That is RVW-3.\n\nThe unsolved part is enumeration. Published delegations let an observer collect every address an identity has used, which is worse than using one address openly. A Merkle commitment with selective reveal stops the enumeration and does not stop timing correlation. Open problem OP-4.", "date_published": "2026-11-09T00:00:00.000Z", "tags": [ "Note" ] }, { "id": "https://revow.org/notes/wrong-ask", "url": "https://revow.org/notes/wrong-ask", "title": "An API is the wrong ask", "summary": "Why every conversation with a licence register stalls, and what to ask for instead.", "content_text": "Every discussion about credential checking arrives at the same place: somebody asks the authority for an API. What comes back is a procurement cycle, a budget line and a wait measured in years, which in practice is a no. The request is then recorded as refused, and everyone concludes that authorities are not interested.\n\nThey were not asked for the right thing. What the problem actually needs is a list of licence references and their status, exported to a file, at an address that does not change. Most registers already produce that export internally, for their own reporting.\n\nAn API is a service: uptime, versioning, authentication, deprecation, a support queue. A file is an artefact: it is produced, it is published, and nothing is owed to anybody afterwards. The gap in cost between the two is enormous and the gap in usefulness, for this purpose, is close to nothing.\n\nThat is what RVW-5 is built around. Tier A is the file. Tier B adds a signature, which costs a key and one DNS record. Only tier C asks for something genuinely new, and the specification is ordered so that an authority can stop at any tier and still have moved the problem forward.\n\nIf you work inside a register and this reads as naive from where you sit, that is exactly the conversation this lab wants to have.", "date_published": "2026-11-09T00:00:00.000Z", "tags": [ "Note" ] }, { "id": "https://revow.org/changelog/anchor-deployed", "url": "https://revow.org/changelog/anchor-deployed", "title": "RevowAnchor is deployed and verified", "summary": "Ethereum mainnet, block 26,379,202. The deployments table in RVW-7 is no longer empty and the document moves to review.", "content_text": "The contract is live at 0x6aA4bfb9f4E370FB9596C09828dEfC819468A792 on Ethereum mainnet, in block 26,379,202, with its source verified on the explorer. The address, the settings used to compile it and the link are in RVW-7.\n\nIt cost 156,191 gas at 0.2 gwei, which is a few cents. That number is worth recording because the argument against deploying early is usually cost, and at this size the argument does not survive contact with an invoice.\n\nRVW-7 moves from draft to review on the strength of it. Review in this lab means the thing is implemented and we are looking for problems with it, which is now true: there is an address anyone can call, read and disagree with.\n\nWhat has not changed: the protocol still works with no chain at all. Claims are files, bindings are DNS records, authority files are CSV. This contract buys a timestamp nobody can move and a withdrawal that propagates in seconds, and an implementation that never touches it is still a complete implementation.\n\nWhat is still missing is an independent read of the source. Fifty lines tested by the person who wrote them is not an audit, and the deployment does not change that.", "date_published": "2026-11-09T00:00:00.000Z", "tags": [ "Log" ] }, { "id": "https://revow.org/changelog/anchor-tested", "url": "https://revow.org/changelog/anchor-tested", "title": "RevowAnchor: the suite is green, and it is still not deployed", "summary": "Sixteen tests pass, including three invariants checked across 128,000 calls each. The deployments table stays empty until there is an address.", "content_text": "The contract specified in RVW-7 is written and tested. Thirteen unit and fuzz tests cover the event, the empty root, the same day anchored twice, two publishers that never collide, the withdrawal and its timestamp, the refusal of a second withdrawal, the fact that a withdrawal only ever touches the caller, and that it is permanent a year later. Two more check that the contract refuses ether and has no fallback, so there is no hidden entry point.\n\nThree invariants run against a handler bounded to five actors and eight claim identifiers, each checked across two hundred and fifty six campaigns of five hundred calls. No reverts, no failures. What they establish is the property that matters: a withdrawal cannot appear, move or vanish without its subject, and anchoring never writes to the withdrawal map.\n\nNone of that is a substitute for an independent read of fifty lines of Solidity, and it is not presented as one. A test suite written by the same person who wrote the contract tests the same assumptions twice.\n\nIt is not deployed. The source and the ABI are published, the deployments table in RVW-7 is empty, and it stays empty until there is an address to put in it.", "date_published": "2026-11-09T00:00:00.000Z", "tags": [ "Log" ] }, { "id": "https://revow.org/changelog/index-trades", "url": "https://revow.org/changelog/index-trades", "title": "Register index: the first shape, before any of it was checked", "summary": "Superseded the same day. Kept because a lab that deletes its wrong drafts is harder to trust than one that leaves them up.", "content_text": "The first version of the index covered twenty-eight registers across nineteen trades and sixteen jurisdictions, from solicitors and notaries to electricians, gas installers, vets, migration agents and insurance brokers.\n\nThe spread was the point, and it still is. An early draft leaned heavily on property, which made the whole lab read as a real estate tool. A conveyancing fraud and a rewired invoice from a tradesman are the same problem in different clothes, and a standard that only serves one trade is a product.\n\nThe assessments in that version were placeholders. They were replaced the same day by registers checked one at a time against the authorities’ own pages, and several of the placeholder judgements turned out to be wrong, France most embarrassingly. This entry is left in place because the superseding one only means something if the thing it superseded is still readable.", "date_published": "2026-11-09T00:00:00.000Z", "tags": [ "Log" ] }, { "id": "https://revow.org/changelog/leading-zeros", "url": "https://revow.org/changelog/leading-zeros", "title": "RVW-1: licence references keep their leading zeros", "summary": "A reference is a string, never a number, and an implementation that parses it will eventually be wrong.", "content_text": "Several registers issue references with leading zeros, letters, slashes or spaces. Any implementation that reads one into an integer loses information and will match the wrong licence sooner or later.\n\nRVW-1 section 3 now says it in the field table: the reference is carried exactly as the authority writes it. Since the canonical form forbids floating point values anyway, nothing in a claim should ever be parsed as a number except the document version.", "date_published": "2026-11-09T00:00:00.000Z", "tags": [ "Log" ] }, { "id": "https://revow.org/changelog/registers-verified", "url": "https://revow.org/changelog/registers-verified", "title": "First verification pass on the register index", "summary": "Forty-seven registers checked by hand. Denmark amended its law so the register records why an approval ended instead of deleting the person. The European Union legislated most of this for one trade in 2006, Italy did it for every regulated profession in 2012, Poland deleted its register in 2014, Estonia has every component of a signed register except the signed file, and three jurisdictions keep the register that counts in a room.", "content_text": "The index now carries forty-seven registers across thirty-three jurisdictions and forty-one trades, each checked against the authority’s own published pages on 9 November 2026, with what was found written out on the row’s page. Health, law, finance, construction, electrical work, gas, security, architecture, migration, property. Several findings were worth the pass on their own, and two of them changed what this lab thinks it is asking for.\n\nFrance was wrong in the lab’s own notes. The working assumption had been that no national public register of estate agents existed. It does: a 2015 decree created a national file of carte professionnelle holders and put CCI France in charge of it, after the card moved from the prefectures to the chambers of commerce. Public, consultable, no export. The grade changed and so did the argument.\n\nQueensland publishes its builders as a CSV and refuses to publish the older versions, stating that it does so to avoid putting out data that is no longer correct. The reasoning is sound and the consequence is severe: you can check a licence today and you cannot establish what the register said on the day the money moved, which is the only question anybody asks after a fraud.\n\nAhpra prices the machine-readable route at four thousand dollars to connect and a thousand a year to keep, and that paid feed refreshes every 24 hours while the free public page refreshes about every fifteen minutes. The programmatic route is slower than the human one and costs money. That is not an authority being obstructive; it is what happens when data access is built as a product for employers rather than as a public artefact.\n\nTexas is the counter-example that makes the whole argument arguable. The Department of Licensing and Regulation publishes a CSV per programme, updated daily, plus an all-licences file covering everything it regulates, with no key and no account. Tier A of RVW-5 is not a proposal there; it is a description of what one authority already does. Nobody had to build a protocol for it to happen.\n\nFour more are worth stating plainly. The UK sells its architects: anyone may search the register free, and a copy of the whole thing is a paid PDF behind a link that expires, with the website and the purchase download listed as two separate items in the board’s own publication scheme. The UK security regulator will not let you search without the licence number unless you supply the person’s date of birth, so checking a credential means holding personal data about them. Australia’s migration authority warns applicants, in its own user guide, to be careful of people pretending to be registered agents, which is this lab’s problem statement written by a government office. And Germany registers more of its tradespeople than almost anywhere while letting the public check almost none of them: compulsory chamber membership, no national lookup, enquiries by telephone, and the enquirer expected to show a legitimate interest.\n\nThen Singapore, which is the one that should be uncomfortable reading for everybody else in the table. The Council for Estate Agencies publishes every valid salesperson as a CSV of around thirty-eight thousand rows, refreshed three times a day, through a documented query API, under a licence that says free forever for personal or commercial use. It publishes the suspended and the revoked as separate lists. It publishes a rolling three-year record of enforcement actions. It publishes the transactions each agent actually completed. Everything this lab spends specifications arguing for, minus the signature, one regulator simply decided to do.\n\nAnd Dubai, which has gone furthest on the thing itself. Every broker carries a registration number, every advert must carry a permit number issued by the regulator, and the advert can be scanned and checked against the registry on the spot. A listing is bound to a licensed person and the binding is enforced with fines, suspension and permanent cancellation. It works, and it is not portable: no open file, the machine route behind a gateway, and the proof living inside one authority’s app rather than in an artefact anyone can verify for themselves. That gap is the whole argument for doing this as a protocol instead of as a product, and it is better evidence than anything the lab could have written.\n\nTwo more worth recording. Ireland keeps the statutory register of practising solicitors inspectable at the Society’s premises in Dublin during office hours; what is online is a directory whose own disclaimer says it should not be regarded as a comprehensive list. The Society has had to post a notice that an AI search tool is producing inaccurate information about disciplinary findings, which is what happens when the authoritative record is the hardest of the three to reach. The Netherlands, by contrast, documents its health register’s machine interface down to the WSDL and publishes the coupling under CC0, and still offers no file, so there is nothing to hash and nothing to sign.\n\nBritish Columbia deserves the last word, because its regulator wrote the best sentence in the index about its own public licensee search: this is an unofficial search. It shows the current licence period and not the licensing history, and anyone who needs an official answer is told to telephone. The same authority runs a consumer campaign telling people to search before they sign, pointing at that search, while agreeing to give a regional realtor association on-demand access to its licensing data in exchange for transaction data. The industry body gets a feed and the public gets a disclaimer. Scotland, by contrast, has most of the shape already: a card, a five-digit number, and a status check that tells anyone whether that number is currently entitled to practise, and says not entitled to practise when it is not. No file, no export, and an answer you cannot keep.\n\nThree findings from the later passes deserve to be read together, because between them they answer most of the objections this lab gets. Italy legislated the hard part in 2012. INI-PEC is a national index, established by statute, holding the certified electronic address of every company in the business register and every professional enrolled in an order, fed by the orders themselves, free and searchable with no credential, and the Digital Administration Code states that consultation of the digital domicile registers is freely permitted, not subject to authentication, and that the lists are produced in open format. Everyone who says no government would ever mandate that every licensed professional publish a verified digital address in one national index should know that one already did, and that the address carries legal weight when something is sent to it. It binds an inbox rather than a key, and that is the only real difference.\n\nEstonia answers the technical objection and sharpens the ask. It has a register of professional certificates refreshed nightly, identities validated against the population register, a citizen view of your own certificates including expired ones, and every message between those systems digitally signed and timestamped with logs admissible in court. Citizens receive signed files from public bodies as a matter of routine and verify them on a laptop. Every component of grade A exists in that country and the grade is still B, because the state signs the channel between institutions and signs documents issued to individuals, and publishes no signed file of who holds what. Sign the artefact, not the channel. Estonia is the proof that those are not the same thing.\n\nPoland is the controlled experiment nobody would have been allowed to run. On 1 January 2014 the central registers of estate agents and property managers lost legal force and were closed, pending applications were discontinued, and the licence, the clean record, the education requirement and the placement all went with them, along with professional liability. Trade federations launched competing voluntary registers to fill the hole. Twelve years on the state is moving back the other way, restoring a central register of property managers with entry required in order to practise, on the stated ground that deregulation in property produced negative effects. When somebody asks what a public credential record is actually worth, that is the citation.\n\nA late addition is worth one line because it states the opposing case better than any critic has. Norway publishes its centrally approved construction firms through a free REST API with no key and no registration, which is as open as this index gets, and asks users not to store the data permanently but to look it up live instead. That request is entirely reasonable: it keeps every answer fresh and it stops stale copies circulating. It is also exactly what a durable proof cannot do. No copy means no provenance, and no way to show, a year into a dispute, what the register said on the day the contract was signed. Freshness and provenance pull in opposite directions, and a signed dated file is the only thing that gives you both.\n\nThree later rows say more about the specifications than anything the lab has written. Denmark used to delete an estate agent from its public register when their approval ended. The law was amended so that the approval is instead recorded as deposited, lapsed, withdrawn or revoked. Somebody worked out that erasing a person destroys the only record that answers the question a disputed transaction actually asks, which is not whether they are approved today but what the register said then, and why it stopped. That is RVW-6, passed into law, by a jurisdiction that had never heard of this lab.\n\nSeoul, facing a wave of lease-deposit fraud, has said it intends to publish detailed business information about practising agents so that risky ones can be identified, and to do it with the agents’ consent. Consent-based enrichment of a public register, for fraud prevention: that is tier C of RVW-5, reached independently, by a city government with a problem rather than a protocol.\n\nAnd Ireland supplies the evidence that impersonation is a real offence rather than a hypothetical. Its utilities regulator has prosecuted people for carrying out gas work while falsely claiming to be registered, including one whose claim was disproved by a records check and, most pointedly, a former registered installer who kept claiming registration after his had been terminated. The credential was real, then it was not, and the only thing between the public and the lie was somebody thinking to check. An ID card with a photograph answers that in a doorway. It answers nothing over email.\n\nWhat this pass does not have yet: archived copies of the evidence with their digests published beside each row. Until that exists a row can be disputed but not checked against a frozen copy, and that is the next piece of work. Corrections are wanted, in particular from anyone who works inside one of these forty-seven.", "date_published": "2026-11-09T00:00:00.000Z", "tags": [ "Log" ] } ] }