TEMPLE’s story is not one mechanism carried forward. It is a succession of launch rituals, retired staking contracts, treasury migrations and policy tools—and the safest reading begins by asking which layer still has power.
TEMPLE arrived through a theatrical launch: Fire Ritual allocations, an Opening Ceremony game and locked, auto-compounding OGTemple staking. Those names are historical architecture, not a menu of current benefits.
The project repository now labels the V1 treasury, Safe Harvest, OGTemple and four exit queues as legacy and unused. Reading the old promise as a live product would turn archaeology into advertising.
The first custom AMM router tried to enforce an intrinsic-value floor and could mint when price rose. A replacement removed protocol minting, while IVSwap patched a floor-calculation weakness before it too was retired.
The modern TPI is a stablecoin-backing metric. RAMOS may act around it, but the project itself says the target is not a hard floor; market price can sit on either side. The reviewed code and product-policy materials do not establish holder redemption at TPI or turn that metric into a legal guarantee.
The canonical contract is 0x470EBf5f030Ed85Fc1ed4C2d36B9DD02e77CF1b7. It has 18 decimals, was at 23,769,704.542254556392728666 supply on 2026-09-05, and contains no maximum.
Its owner is 0x4D6175d58C5AceEf30F546C0d5A557efFa53A950, a Safe requiring signatures from 2 of 4 registered owner addresses. The identities behind those addresses remain unproven here. The Safe can change CAN_MINT accounts; those accounts can inflate supply, while holders can burn their own balance. Because the role is not enumerable here, a complete current minter list remains unproven.
RAMOS historically held a 50/50 TEMPLE/DAI Balancer position. Around policy bounds it can withdraw and burn TEMPLE, add liquidity or extract stablecoins; bots may trigger the permitted functions.
That is active treasury management, not mechanical backing. The main token-owning Safe, executor Safe and rescuer Safe occupy different roles, and reviewed materials do not show every governance decision passing through automatic token voting or a timelock.
Today staking TEMPLE earns TGLD. TGLD is a separate, nonstandard auction currency with a 1 billion maximum and 70% auction, 15% staker and 15% team-Safe emission allocation.
Spice Bazaar uses TGLD to auction treasury assets excluded from stable backing. That loop may give TEMPLE utility, but it does not give every TEMPLE holder title to those assets or turn TGLD emissions into guaranteed yield.
On 2022-10-11 an attacker drained roughly $2.3 million from the affiliated STAX staking vault through an access-control failure. Later reporting traced the proceeds into Tornado Cash.
The scope matters: STAX was an adjacent staking product, not the canonical token contract. The incident still belongs in TEMPLE history because product integration can expose holders to contracts outside the token’s narrow code surface.
A TEMPLE balance can be transferred, burned, staked or used in available protocol paths. The reviewed sources do not promise redemption at TPI, a share of the treasury, company equity or a fixed return.
“Encore” also stops at the evidence boundary: no official current component by that name appeared in the docs, registry or repository. Same-name protocols are excluded until a primary TempleDAO source connects them.
On-chain allocations and a FRAX-for-TEMPLE presale opened the project’s first chapter.
Game-gated purchases, LockedOGTemple and auto-compounding staking defined the early holder experience.
PeckShield’s dated AMM audit records the security review of the intrinsic-value-era exchange machinery.
The affiliated STAX staking vault lost roughly $2.3 million; the core TEMPLE contract was not identified as the exploited code.
The V2 repository separated executor, treasury vault, strategies and rescue functions from the legacy treasury.
Temple Gold’s staking, auction and governance surfaces received a public review cycle.
Last evidence review: 2026-09-05
TempleDAO is an Ethereum treasury protocol organized around TEMPLE, TPI-guided treasury policy, RAMOS liquidity operations, TLC credit and the TGLD-based Spice Bazaar. Its current token is distinct from its retired ritual launch, OGTemple staking and custom-AMM machinery.
TempleDAO’s language of intrinsic value can sound like a redeemable floor. The evidence shows a policy metric and administered market operations instead: price can depart from TPI, mint authority exists, and a holder has no documented direct claim on the treasury.
TEMPLE is an 18-decimal ERC-20. A 2-of-4 Safe owns it and can grant or revoke CAN_MINT; minters can create tokens and holders can burn their own. RAMOS can adjust protocol-owned liquidity around TPI. Staking now emits separate TGLD for auctions, while executor and rescue roles operate through additional Safes.
No. It is a stablecoin-backing metric used by policy machinery. The RAMOS page explicitly says TEMPLE may trade at a discount or premium.
Yes in principle. Accounts holding CAN_MINT can mint, and the 2-of-4 owner Safe can add or remove minters. No hard cap exists.
The current guide pays TGLD emissions to TEMPLE stakers. TGLD has its own supply formula and rights; it is not newly minted TEMPLE.
No. The project repository classifies them with Fire Ritual, Opening Ceremony and exit queues as legacy deployed contracts.
The reported incident targeted the affiliated STAX staking vault. It demonstrated ecosystem and access-control risk, but not a flaw in the canonical token contract.
No such current component was found in official docs, the contract registry or repository. This dossier does not merge unrelated Encore projects into TEMPLE.
No reviewed source grants redemption at TPI, ownership of treasury assets, equity or guaranteed yield.
Choose a tracking site for TempleDAO:
