hi there, she.

good to see we are running tests before mains to the net

could you update here in a couple of days time to time how it's going

and inform us with the good news of the mainnet launch

ill will give it a go with the testnet and see how the software looks out to be overall

(maybe im glad to be able to check the testnet out for the first time look around and maybe the mainnet will more inviting)
 

Lots of work done last night - finalisation of the consensus rules on test-net.

Previously researched the possibility of 9 second blocks with 0.1 rewards. This proved a load on the scalability so we are reverting to the optimal 1Shear /90second block time and chronoflux still does the pruning work to keep the chain lean and usable.

Baked in 6 confirmations til spendable (policy recommendation of 12) and applied the tx fee structure (more on this later).

recutting clients to the new rules now... watch this space!

Good news!
The final touches are being implemented in testnet and we are on-schedule to launch in 3 days time.

With excellent privacy preserving mechanisms like silent addresses and stem/fluff at node level, no user info is broadcast and we have implemented some excellent security measures to ensure your coins are your coins with no exceptional vulnerabilities in the project.

We look forward to welcoming miners on Friday 11th September at 9PM BST.

Docs section has been added to the website, as well as the Shear white paper.

UPDATE!

The first coin to mint and prove a separate hash bonus in the coinbase and make a missing dest invalid:
SHEAR on shear-testnet-v2
at testnet block height 1479.

Now it's time for the serious work.

Shear Admittance — naming lock for the full Shear anon set
=======================================================

Date: 2026-09-12

ONE-LINE
--------
Admit proves a spend is an admissible extraction from the committed
current J without revealing which flowline carried it.


CHRONOFLUX MAP (motivation only — not a consensus string)
---------------------------------------------------------
Principia primitive:  div J = 0,  J = rho_t * u
A configuration is admissible iff evolution preserves that relation.

  Principia                         Shear Admit
  --------------------------------  --------------------------------
  temporal density rho_t            live output density (the fluxset)
  flow u                            worldline of a spendable output
  current J                         committed spendable set
  admissible configuration          spend that verifies against the current
  commitment to J                   tree root (jroot)

LOCKED NAMES
------------
Layer                  Name                 Notes
---------------------  -------------------  ------------------------------------------
Public / user copy     Admittance           "Admittance hides which output moved."
Long form              Shear Admittance     spec titles, CCS-style write-ups
Consensus / tx type    AdmitV1              first live type; bump to AdmitV2 on
                                            breaking statement change
Crate / module         shear-admit          from the principals 'admissibility' fundamentals
Live output set        fluxset              the set Admit proves against
Accumulator root       jroot                commitment to J as of a reference height
Proof blob             admit_proof          opaque bytes; length from input count
                                            + tree depth
Construct / verify     admit_prove          FFI and daemon
                       admit_verify

SPEC HEADER (paste into protocol notes)
---------------------------------------
Admit v1 — Shear admittance proofs
Operator cites: Curve Trees (Campanelli, Hall-Andersen, Kamp,
              USENIX Security 23 / ePrint 2022/756)
Statement   : spend is admissible in J = rho * u over the fluxset
Auth        : Shear spend-key / EIP-712 intent
Linkability : Shear native (dest / spend-tag as already specified);

EXPANDED CITATIONS
----------------------------------------------------------
- Accumulator: Campanelli, Hall-Andersen, Kamp — Curve Trees: Practical
  and Transparent Zero-Knowledge Accumulators, USENIX Security 23,
  ePrint 2022/756.
- If divisor gadgets or Parker leaf/SA+L split are used: cite Parker
- Reviews of those gadgets stay attributed to their authors
  (Cypher Stack / Veridise / etc.). They are not "Admit audits" until
  they cover Shear's statement.

Allowed in prose:
  "Admit instantiates Curve Trees."
  "Motivation is Chronoflux continuity."


DOC SENTENCE BANK
-----------------
User:  Admittance hides which output moved.
Spec:  Admittance proves a spend is an admissible extraction from the
       committed current J without revealing which flowline carried it.
Audit: Admit v1 is a Curve Trees membership proof over Shear's fluxset
       plus Shear spend-auth.

IMPLEMENTATION NOTES
-----------------------------------------------------
- Helios/Selene exist to tower Ed25519. If Shear's base curve is not
  Ed25519, pick a cycle for that field or accept a worse in-circuit
  hash.
- Public amounts now depreciated (Shear privacy goal: amounts hidden, dests stealth, full anon set)
- Tree grow/trim/reorg, reference height, and unlock rules are Shear
  consensus — write them under Admit.

DINS-DAG and the Private Mining Corp

Mining should feel like joining a company that pays you for real work — not like hoping you were on the lucky template when the block closed.

That is the idea behind DINS-DAG, and the reason we talk about Shear's mining layer as a Private Mining Corp.

The problem we are fixing

On many pool-based chains, your shares live in one operator's memory. If another template wins the seal race, honest work can evaporate as "lost round." The pool that found the block gets to decide what counted. Community miners feel that as AFK unfairness: you hashed, you were eligible… then the books shrugged.

Shear already pays a scheduled block pot and a hash bonus for proven, destination-bound work. DINS is how we make that bonus behave like network law, not pool luck.

What DINS-DAG is

DINS stands for Deterministic Inclusive Network Settlement.
Your proven, destination-bound shares enter a shared network window everyone can re-check — not a private pool list that dies when someone else seals. Settlement is deterministic (any full node recomputes the same payroll) and inclusive (eligible in-window work still counts when a competing template wins the seal race).

DAG stands for Directed Acyclic Graph.
Here that means a share-DAG: mining proofs link as a growing graph of work on top of Shear's linear block spine (the familiar ~1 SHE per block continuity). Tips advance. At seal, the chain commits a deterministic "blue" view of that graph. Any honest seal of the window settles the same eligible work. Competing seals stop being a reason to zero people who already proved in-window hashes.

So DINS-DAG = fair, consensus-ruled mining settlement, organised as a share graph instead of a single pool's forgotten round.

In plain terms:

• You mine to your payout destination.
  
• Your work gets a network-visible receipt in the window.
• When a block seals, settlement is recomputable by any full node — no trusted "pool said so" oracle.
  
• Losing the template race should not erase eligible work that was already in the window.

The pool still matters. Stratum, difficulty smoothing, the HUD, Continuum — that operator UX stays. What moves is mint authority for hash bonus: from "this pool's open round at seal" toward consensus settlement from the share-DAG.

Why "Private Mining Corp"

Think of the network as a tightly run co-op that only admits cryptographically proven labour:

• Membership is your dest-bound proof, not a KYC form.
• The "payroll" is deterministic settlement at seal — Window credit becomes sealed landings, then spendable after confirmations.
• Books stay readable: Window → Sealed → Spendable, with your own blue detail in Continuum when you want it.
  
• The full network graph belongs on surfaces like dag.shear.digital; your wallet shows your books, not everyone else's leaves.
  

Private, because payouts stay tied to Shear's confidential note model and dest-bound proofs — not a public scoreboard of who owes whom in plaintext. A corp, because the rules are shared, capped, and boringly fair: same emission schedule, clearer who gets paid when the block lands.

What we are not claiming

This is the product direction we are building toward on Shear's testnet stack — design-hardened, spike-first, fail-closed. We are not promising a magic APY, an uncle-block casino, or a second full blockchain. Emission stays honest; DINS chooses eligibility, it does not print extra SHE for vibes.

No oracle mint. No double-pay paths. Caps so the graph cannot DoS the chain. Privacy hard lines stay: the window is not a place to dump raw addresses or open amounts.

Why it is worth the enthusiasm

If DINS-DAG lands the way we intend, Shear mining feels less like gambling on which pool won the race, and more like holding equity in a private corp that actually books your shift.

Hash. Prove. Land in the window. Seal. Get paid under rules everyone can re-run.

That is the Private Mining Corp. That is DINS-DAG.

— Shear

Last step done before Mainnet prep.

Chain. Testnet-v5 was reset and is producing.
Pool and the operator node fleet sit on the same tip: height, hash, ibd=false, miners on stratum 1111, sequential ingest 1 → 2 → … with full seal checks (ADMITv2 + DINS-DAG pot and hash bonus). Empty-batch genesis seals; hash bonus is share-batch units only.

Privacy. The book only records ssa1 dests. Continuum accepts she1, ssa1, and shear1 in To: full she1 becomes a one-time silent dest; ssa1 is itself; your own shear1 settles on destCommit (the spendable mailbox). Short she1 fingerprints stay unpaid. Rest-frame strings never go on chain.

Balances. Spendable is reconstructOwner on sealed notes after 6 confirmations.

Pending/unconfirmed is the pie until then. Owed-π is not spendable. Combined Continuum figure is the sum of those dest notes, so you can receive on any of the three identities and spend what the node actually verifies.

NODEv7 / Continuum 0.56. Source on main matches this chain. Users need a fresh node datadir.

@everyone - we have reset the chain again, so you will need to delete your old wallet versions and install 0.56 fresh.

NODE: https://github.com/rgsneddon/shear-testnet/releases/tag/v7

WALLET: https://github.com/rgsneddon/shear-testnet/releases/tag/0.56

Shear update: new dates for the v12 testnet and mainnet

Hi all,

A quick update on where we are and when things are landing.

The short version: mainnet is moving from 16th November to Monday 21st December 2026 at 2pm UK time. The v12 public testnet is now expected in early December.

Why the change? While hardening v12 we found and fixed more than we expected, and one of the things we found was serious enough that we want it fixed, tested and running on testnet for a good while before mainnet. We would much rather ship a chain that works properly than hit a date. The new date gives the v12 testnet at least a week of real use, and some room to spare, before mainnet goes live.

Here's the order things happen in:

1. Finish the remaining work below (through November)
2. Run a fast-block private test network, where we use every feature on desktop and Android and fix anything that breaks (from around 27th November)
3. Launch the v12 public testnet (around 3rd December)
4. At least 7 days of the v12 testnet running under real use (to around 10th December)
5. Mainnet genesis: Monday 21st December 2026, 2pm UK time

What's still being worked on, with the date each piece should be done:

- Network and block-integrity hardening, including a fix that makes sure every block commits to exactly the transactions inside it: around 28th October
- Vault lock safety, so a lock can only ever be withdrawn by its owner: around 30th October
- Command-line wallet fix for Vault locks: around 31st October
- Mining hash safety, so the native hasher can't crash and works on older CPUs: around 2nd November
- Correct network settings everywhere, so testnet, mainnet and dev networks can never get mixed up: around 4th November
- Signed name registration: around 5th November
- Stricter checking of data arriving from the network: around 7th November
- Fairer share credit for miners: around 8th November
- The private miner payout: around 9th November
- Extra privacy hardening for spends: around 10th November
- Moving our tests over to real chain data for every consensus path: around 13th November
- Private tokens. Anyone will be able to create their own private token, with a fixed supply that can never be added to and the same privacy as SHE. The design is written and reviewed first, then built: around 19th November
- The rest of the test suite moved over to real chain data: around 21st November
- Bringing five older pieces of work up to date (gas limits, reward claims, withdraw rules, Vault fees in the wallet, and the launch checklist): around 25th November
- Clearer wording and polish across the wallet: around 27th November

These dates are our best estimate, not promises. Each step gets reviewed and tested properly before it lands, and if testing turns up a problem we fix it first. If anything moves, we'll tell you.

Thanks for sticking with us. Every one of these steps is about making sure Shear is solid on day one.

The Shear team