Latest verified engineering — 25 October 2026
Windows local password and per-device identities have passing local tests, but are not equivalent to verified production ENTITY single sign-on across FarmNode Host, Bridge, Exchange and Studio. Device consent is distinct from economic participation.
Oct 25 full engineering record · Contribution/use economy · Council qualification
What the user should experience
One authoritative BTG account identity should be recognized consistently by Bit Trade Global, Bridge, FarmNode Host and Studio. Each device uses its own protected key and each application has separate permissions. Re-entering the same email and password into four disconnected local databases does not create true single sign-on.
Device registration
When someone signs in through a trusted account service, the account's authenticated subject can authorize a new device. The Windows FarmNode research app now protects a persistent device signing key using the logged-in Windows user's DPAPI and an encrypted account envelope. Its local device recognition and preservation through migration have passing tests. Equivalent independently proven iOS/Android protection, remote enrollment and online revocation are not yet established.
ENTITY owner proof
The original ENTITY namespace, issuer, manifest and revocation status establish a separate owner-signature chain. A self-declared local FarmNode research account is not the same as original owner authority. Production owner binding must be verified cryptographically and revoked when required, not inferred from a matching email.
Scoped rights
Signing in identifies the person; it does not permit all operations. ENTITY grants are purpose-, product-, device- and resource-specific. Bridge consent is distinct from an Exchange investment right. An Exchange-listed security is not necessarily a licence to execute circuits. Compute entitlements must have separate scope, expiry, quota and resource checks.
Verified position
Local Windows device identity 5/5 focused tests passed and related 97/97 regression passed on 24 October. The current engineering handoff records no completed central identity gateway, verified five-product sign-on, production owner binding, hosted account mapping or qualified mobile pairing. Preserve those distinctions in all public claims.