Verified held signs
Public ownership becomes deterministic context for an Aura page.
Proof pattern
How Simastry uses verified Zodiac context.
Simastry is an astrology app pattern for Zodiacs SDK: a shareable Aura page can include verified held signs, and that same read-only context can optionally shape conversations with AI astrologists.
The product surface.
An Aura page already gives a person a visual and conversational identity surface. Zodiacs SDK adds a factual layer beside the birth chart: signs the person holds through official Zodiacs ownership.
The app decides how to interpret those signs. The SDK provides official registry verification, public ownership reads, identity context, and icon assets.
Aura page
The app can render a held-sign layer beside chart context.
AI astrologists
Conversation prompts can include held signs when the user opts in.
Read-only posture
No custody. No signing. No transactions. Public reads only.
SDK shape.
import { getCrossChainZodiacsOwnership } from "@zodiacs/sdk";
import { getZodiacIdentityContext } from "@zodiacs/sdk/identity";
const ownership = await getCrossChainZodiacsOwnership({
solanaOwner,
baseOwner,
connection,
publicClient
});
const auraContext = getZodiacIdentityContext(ownership, {
sunSign: "leo"
});
const simastryAura = {
surface: "shareable Aura page",
heldSigns: auraContext.heldSigns,
currentSeasonHeld: auraContext.currentSeasonHeld,
aiAstrologistContext: "optional"
};Why it matters.
Birth charts describe what someone was born with. Zodiacs can describe signs they choose to carry. Simastry can place both forms of context in a single Aura experience without turning the SDK into a reading engine.