UpveraTechnology
upvera.co ↗
UTR-26-01Proof EngineWork read at the source. Never typed in.UTR-26-02Value EngineSame events, same rule, same number. With a receipt.UTR-26-03Day RootsSealed every minute. Rooted every day.UTR-26-04Upvera IDOne person. A different key for every door.UTR-26-05Trust SignalsServer time, bots that never count, no small groups, one number everywhere.

Upvera Technology

Built to be checked.

Upvera keeps the record of how companies are built. What happens on it is sealed every minute, and every day ends in a root that anyone can check, starting with you, on this page.

Check the chainRead the reports
Day root · 2026-10-21

9 days chained to the genesis of 2026-10-13. Published to GitHub, timestamped with OpenTimestamps.

Most platforms ask you to trust their numbers. Upvera gives you ways to check its own.

Proof EngineEvidence, not claims.There is no field where a founder types traction. Work is read where it lives, from sources the founder has to own.Trust SignalsShown equals true.Every number is computed once, on the server, and every surface draws that same number.Rule registryRules change in public.Every rule that touches money, value or privacy is versioned and fingerprinted, and every day root names the rules it was sealed under.Upvera IDAn agent may write. A person publishes.AI connected to Upvera can read and draft. The publish button exists only where a person presses it.

Five systems

What runs underneath.

UTR-26-01Proof EngineWork read at the source. Never typed in.System reportReadUTR-26-02Value EngineSame events, same rule, same number. With a receipt.System reportReadUTR-26-03Day RootsSealed every minute. Rooted every day.System reportReadUTR-26-04Upvera IDOne person. A different key for every door.System reportReadUTR-26-05Trust SignalsServer time, bots that never count, no small groups, one number everywhere.System reportRead

UTR-26-01Upvera Proof Engine

Evidence, not claims.

A startup's progress is read from the places work actually happens. Repositories, store listings, deployments, revenue tools and the product itself, each one tied to a verified owner.

Read the report
Work is read at its source, passes an ownership check and is appended to the proof history. A typed claim has no way in.Where the work livesGitHubrepositoryApp Storestore listingGoogle Playstore listingVercel · Netlifydeploymentsnpm · PyPI · crates.iopackagesHugging FacemodelsRevenueCat · App Store Connectrevenue bandThe product itselfobserved by the Eye“We hit 10,000 users.”a typed claim · exampleno input for claimsOwnershipVerified ownerDNS TXT record/.well-known fileGitHub AppThe recordproof history · append-onlyRepository activityVersion live on the App StoreProduct stage observedRevenue band readShip chain sealedValue Engine · Proof mass

UTR-26-02Upvera Value Engine

Every number has its reasons.

Value Engine 3.0 is a pure function of events and a rule. Integer arithmetic, one Rust codebase compiled natively and to WebAssembly, byte-identical results. Every change arrives with its reasons, and the reasons add up.

Read the report

Receipt · Upvera · 24 hours

345.26359.93

+14.668908

  1. Worknew posts and shipping drew a response+12.539872
  2. Momentumnew events raised its pace against its own average+3.024910
  3. Peopleindependent people engaged+1.562561
  4. Peopletrust of the people engaging rose+0.995928
  5. Other7 small reasons−0.569189
  6. Catch-upvalue hasn't caught up with its new target yet−2.885174
Rows add up to +14.668908 = the changevalue@1 · engine 0.1.0 · inputs b1d3f2b2

A real receipt, served by the public Value API for Upvera's own startup. Captured 2026-10-22 12:01 UTC.

UTR-26-03Upvera Day Roots

History that can't be quietly rewritten.

Both of Upvera's ledgers are sealed into minute blocks. Each day ends in one root, chained to the day before, published to GitHub and timestamped with OpenTimestamps. Digests only. No counts, no names.

Read the report
Minute blocks are hashed pairwise into one daily root. The root, the previous day's digest and the rule registry head are written to the day file, which is published to GitHub and timestamped with OpenTimestamps.A day of minute blocksminminmin……minminminhhhhhhroot 28f8cbsha-256 · RFC 6962 Merkle tree · leaves carry aliases and salted commitments, never namesThe day file · 2026-10-21day2026-10-21preveb16b5ff…73b7root28f8cb9f…f625tip21039fbb…2cc6checkpointf1f4ccb5…974erules_hash5ae2f2cf…359cregistry head at days@1GitHubupvera-co/ledger-rootsOpenTimestampsanchored in Bitcoin

UTR-26-04Upvera ID

One account. A different identifier for every site.

Sign in with Upvera tells a site how strongly a person is verified, and gives every site a different identifier for them. AI clients connect over OAuth, read what you allow and draft. Publishing stays with you.

Read the report
One person signs in to three apps through Upvera ID. Each app receives a different identifier, so the apps cannot link the person. Below, an AI client can read and draft, while publishing stays with the person.One personYouhow strongly you are verifiedunsignedweb keydevice keydevice attestedUpvera IDid.upvera.coOpenID Connect · ES256What each site receives · example identifiersnotes.examplesub q7Zt1VhB0sKc2mWfE4yR8nhiring.examplesub Lr3uX9aPe6TgN1dQ5bJw0kevents.examplesub Ys8Hc2Kv4nM7xRb1ZpF6tAThree sites, three identifiers. Nothing to compare.AI access over MCPAI clientconnects with OAuth 2.1Reads and draftsonly what you allowedPublisha card only you can presspublishing is offeredonly to the cardAn agent may write. A person publishes.

UTR-26-05Upvera Trust Signals

Signals you can't buy.

The server stamps the time. Every actor is classified the moment it acts, and bots never enter learning. Private activity appears only in groups of five or more, and visibility can't be bought on any plan.

Read the report
Events pass four gates before they become a signal: the server sets the time, bots are removed, private kinds appear only in groups of five or more, and public wings appear after a delay and only with consent.Events · examplesServer timeNo botsGroups of fiveDelay and consentSignalPrimepersonCommentpersonFollowbotnever countedViewpersononly in groups of 5+Wingpersonpublic after 7 days, if opted inThe time is stamped by the server. A client cannot backdate anything.

Open verification

Don't take our word for it.

Three ways to check Upvera without trusting Upvera. The first two need no account; the third checks your own activity.

01 · In this browserRecompute the chainEvery day file is fetched from GitHub and hashed here, from genesis to October 21, 2026.No account · reads public filesRun it
02 · On your machineOne command, no networkgit clone https://github.com/upvera-co/ledger-roots
node ledger-roots/tools/days.mjs verifyNode 20+ · no dependenciesRead the tool
03 · Your own recordFind yourself in a sealed dayTake a proof on app.upvera.co and check it at upvera.co/dogrula, in your browser, against the public root.Rust verifier · WebAssemblyOpen

Now running

Rules ship like software.

Every rule that touches value, money or privacy has a version, a fingerprint and a moment it took effect. The October 21, 2026 day root names the registry it was sealed under.

Rule registry chain54 links

54 rule versions, each chained to the one before it.

RuleWhat it governsIn force since (UTC)Fingerprint
days@1LiveBuild days One definition of a build day and a streak, read from the event record.abe584c9b008
eco@1LiveEcosystem frame How startups are linked on the ecosystem map.fb9605d3f514
record@1LiveFounder record Facts with receipts. No score.c17de77fd745
scout@1LiveFirst wing A record of who supported a startup early.31469f25c95c
value.shadow@3In shadowValue shadow A candidate value rule, running beside the live one.1e0aba5827bc
money@20LiveMoney surface The functions that move UPV, fingerprinted together as one surface.0bbd7c69ec71
value@1LiveValue Engine The rule that computes Upvera Value.d7b02301311a
watch@13LiveWatcher The hourly invariant checks and the alarm behind them.6ccd09bb5bad
trust.disclosure@1LiveDisclosure What a published proof is allowed to reveal.733987c675c5
block@1LiveBlocks How minutes are sealed and what a day file contains.db31bee24527
econ@2LiveIssuance limits Caps on what the platform may issue, enforced in the same transaction.09db2ecdcf89
trust.class@0LiveActor classes Who acted, classified at the moment of the event.512072974ee7
All 54 versions in the archive

Guides and tools

Answers you can use today.

Practical pages for founders, developers and anyone checking a claim. The tools run in your browser and send nothing to Upvera.

ToolCanonicalize JSON (RFC 8785) and hash itTurn any JSON into its RFC 8785 canonical form and SHA-256 it, in your browser, with a real example that links one day to the next.DevelopersUse itToolCheck a domain's TXT records and verify you own itLook up any domain's TXT records from your browser, see which verification tokens are live, and fix the mistakes that make verification fail.FoundersUse itToolHide small groups in a published table (k-anonymity)An editable table that applies primary and complementary suppression, so small groups stay hidden even when totals are published.DevelopersUse itToolMake rounded numbers add up to the totalWatch rounding each line miss the total on a real receipt, then fix it with the largest remainder method or a running total.DevelopersUse itToolVerify a Merkle inclusion proof (RFC 9162)Recompute a log's root from one leaf and its audit path in your browser, with a real Sigstore entry, and see which side each step takes.DevelopersUse itGuideHow to check a startup's claims before you believe themA checklist with public tools for domain age, site history, store listings, code, packages, team and revenue, plus red flags.Anyone checkingRead
All 14 guides

Research

Written down, numbered, dated.

  1. UTR-26-01Upvera Proof EngineWork read at the source. Never typed in.System report2026-10-20
  2. UTR-26-02Upvera Value EngineSame events, same rule, same number. With a receipt.System report2026-10-20
  3. UTR-26-03Upvera Day RootsSealed every minute. Rooted every day.System report2026-10-20
  4. UTR-26-04Upvera IDOne person. A different key for every door.System report2026-10-20
  5. UTR-26-05Upvera Trust SignalsServer time, bots that never count, no small groups, one number everywhere.System report2026-10-20
  6. UTR-26-06Rules released like softwareHow Upvera versions, hashes and chains its UPV, value, privacy and watcher rules, and why a new value rule runs in shadow first.Verification2026-10-20
  7. UTR-26-07Kestrel: measure before you fixHow Upvera's performance program measures each screen, closes whole classes of problems, checks its own tools and accepts speed fixes only on counts.Engineering2026-10-20
  8. UTR-26-08An AI that never sees the numberHow Upi runs Upvera's assistant through one gateway, draws every number from live data, reserves cost before each call and leaves publishing to people.AI2026-10-20
  9. UTR-26-09Upvera Prism: learning only from peopleHow Upvera Prism orders Discover and Home: server-side signal weights, fused sources, built-in diversity, no bots in learning and a reset you control.Personalization2026-10-20
  10. UTR-26-10The Eye: observing a product with rules, not a modelHow the Eye reads a startup's verified site with fixed rules, tells a real release from a text edit or a rebuild, and keeps a screenshot history of its store listing.Verification2026-10-21
  11. UTR-26-11Roots, not numbersWhy Upvera's day files hold only roots, how leaves are built to be safe to show, and what each person can prove about their own record.Verification2026-10-21
  12. UTR-26-12Seen: matching words to the workHow Seen turns a founder's post into checkable claims, looks for each one in verified sources with fixed rules, and stamps only what it finds.Verification2026-10-21

Today is being sealed.

Since 2026-10-13 15:57 UTC, what happens on Upvera has been sealed into minute blocks, the blocks into days and the days into one chain. Tomorrow there will be one more root to check.

See UpveraBuild on Upvera