Developer Ecosystem · OLGNS Labs · 2026–2027

OLGNS Developer Roadmap

Build · Integrate · Contribute · Grow — a developer-focused program for documentation, open-source tools, ecosystem applications, security research, and community contributions on Anubis Eska Chain.

Planned program · every item below is a target until published and verifiable
Network & RPC

Anubis Eska Chain, read live

These values are fetched from the public Anubis RPC endpoint in your browser right now. Nothing on this page is a cached or hardcoded figure.

Checking RPCRefreshes every 15s · read-only
Chain ID
Latest block
Block timestamp (UTC)
Gas price (gwei)
Token
Token decimals
Total supply
RPC client
Staking fee
Withdrawal fee
Contract paused
Proxy implementation
wallet_addEthereumChain · js
// Add Anubis Mainnet to any EIP-1193 wallet
await window.ethereum.request({
  method: "wallet_addEthereumChain",
  params: [{
    chainId: "0x1a3a", // 6714
    chainName: "Anubis Mainnet",
    rpcUrls: ["https://rpc.anubispace.org"],
    blockExplorerUrls: ["https://browser.anubispace.org"],
    nativeCurrency: { name: "ANUBIS", symbol: "ANUBIS", decimals: 18 },
  }],
});
eth_blockNumber · bash
# Latest block number from the public Anubis RPC
curl -s https://rpc.anubispace.org \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'
Contracts & ABIs

Verified addresses and the live interface

Copy the addresses, download the Origin Earn ABI, and verify every byte on the Anubis explorer before you integrate.

ContractAddressNotes
OLGNS token (ERC-20)
0xa9E7EBA6D6A3aE6ca1286a0264a216EA36767e25Explorer
Standard ERC-20. Use for balances, allowances and approvals.
Origin Earn proxy (ERC-1967 / UUPS)
0xe3E08782D6488F80aA909339EE8c338E3e58Eb1EExplorer
The only address user transactions should ever target.
Current implementation
0xE9B6C8e8E804dD9E49E9DDEccDC22a466224e09cExplorer
Informational. Read the ERC-1967 slot at runtime instead of pinning this value.
OLGNSOriginEarn · v1.2.0-Monthly-Rate · ERC-1967/UUPS · 29 functions
function STAKING_FEE_BPS() view returns (uint256)
read0xcd53bf53
function WITHDRAWAL_FEE_BPS() view returns (uint256)
read0x3a4ae669
function minimumStake(uint8) view returns (uint256)
read0x796a486c
function rewardRate(uint8) view returns (uint256)
read0xabb19309
function durationForPlan(uint8) view returns (uint256)
read0x0563385a
function calculateFixedReward(uint8,uint256) view returns (uint256)
read0xa85dabbe
function flexRewardOf(uint256) view returns (uint256)
read0x51ef72d1
function getUserPositionIds(address) view returns (uint256[])
read0xeddf7570
function getPosition(uint256) view returns (tuple)
read0xeb02c301
function availableRewardLiquidity() view returns (uint256)
read0x6575a08f
function fixedRewardLiability() view returns (uint256)
read0xb171daee
function totalRewardCapacity() view returns (uint256)
read0xfb68b9ca
function paused() view returns (bool)
read0x5c975abb
function owner() view returns (address)
read0x8da5cb5b
function stakingFeeWallet() view returns (address)
read0x1ab7bdde
function withdrawalFeeWallet() view returns (address)
read0x3fea9c40
function treasuryWallet() view returns (address)
read0x4626402b
function olgns() view returns (address)
read0xf217de53
function contractBalance() view returns (uint256)
read0x8b7afe2e
function version() view returns (string)
read0x54fd4d50
function fixedMonthlyRateBps(uint8) view returns (uint256)
read0xffe8a724
function fixedRewardPeriods(uint8) view returns (uint256)
read0x638b0678
function fixedRewardClaimable(uint256) view returns (uint256)
read0x3affa522
function fixedRewardClaimed(uint256) view returns (uint256)
read0xaa6bc93f
function claimFixedReward(uint256) nonpayable
write0xe534c874
function stake(uint8,uint256) nonpayable
write0xdd752e55
function withdrawFixed(uint256) nonpayable
write0x38a9a686
function claimFlexReward(uint256) nonpayable
write0xe7422bb0
function withdrawFlexPrincipal(uint256,uint256) nonpayable
write0xb28bd119
read-balance.ts (viem) · ts
import { createPublicClient, http, defineChain, formatUnits } from "viem";

export const anubis = defineChain({
  id: 6714,
  name: "Anubis Mainnet",
  nativeCurrency: { name: "ANUBIS", symbol: "ANUBIS", decimals: 18 },
  rpcUrls: { default: { http: ["https://rpc.anubispace.org"] } },
  blockExplorers: { default: { name: "Blockscout", url: "https://browser.anubispace.org" } },
});

const client = createPublicClient({ chain: anubis, transport: http() });

const balance = await client.readContract({
  address: "0xa9E7EBA6D6A3aE6ca1286a0264a216EA36767e25",
  abi: ["function balanceOf(address) view returns (uint256)"],
  functionName: "balanceOf",
  args: ["0xYourAddress"],
});

console.log(formatUnits(balance, 18), "OLGNS");
read-live-fees.js · js
// Live protocol parameters — never hardcode fees in your integration
const call = (data) => fetch("https://rpc.anubispace.org", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    jsonrpc: "2.0", id: 1, method: "eth_call",
    params: [{ to: "0xe3E08782D6488F80aA909339EE8c338E3e58Eb1E", data }, "latest"],
  }),
}).then((r) => r.json()).then((r) => BigInt(r.result));

const stakingFeeBps = await call("0xcd53bf53");
const withdrawalFeeBps = await call("0x3a4ae669");
Quickstart

Connect a wallet and read OLGNS

A working example, not a snippet in a document. Connect below and the panel performs the same calls shown in the code.

Working wallet example

This runs the exact flow in the code beside it: connect an EIP-1193 wallet, check the chain ID, and read live balances from the public RPC. Read-only — nothing is signed or sent.

connect-and-read.js · js
const [account] = await window.ethereum.request({ method: "eth_requestAccounts" });

const chainId = await window.ethereum.request({ method: "eth_chainId" });
if (chainId !== "0x1a3a") {
  await window.ethereum.request({
    method: "wallet_switchEthereumChain",
    params: [{ chainId: "0x1a3a" }],
  });
}

// balanceOf(address) — the same read this panel performs
const data = "0x70a08231" + account.slice(2).toLowerCase().padStart(64, "0");
const raw = await window.ethereum.request({
  method: "eth_call",
  params: [{ to: "0xa9E7EBA6D6A3aE6ca1286a0264a216EA36767e25", data }, "latest"],
});

console.log("OLGNS:", Number(BigInt(raw)) / 1e18);

Integration rules: always target the Origin Earn proxy, never the implementation; read fees and plan parameters from the contract instead of hardcoding them; use BigInt arithmetic; and treat the chain as the source of truth for every balance, timestamp and reward figure.

Developer roadmap

Four phases, from documentation to ecosystem

Dates show the planning sequence. A date passing does not mean the phase was delivered.

  1. Q4 202601

    Phase 1 — Developer Foundation

    • Launch a dedicated developer portal.
    • Publish Anubis network setup and RPC documentation.
    • Publish OLGNS token and Origin Earn contract documentation.
    • Provide verified contract addresses, ABIs, and integration examples.
    • Create a developer Discord or community channel.
  2. Q1 202702

    Phase 2 — SDK & API Tools

    • Develop an OLGNS JavaScript/TypeScript SDK.
    • Provide wallet connection and network-check examples.
    • Build read-only APIs for token and ecosystem data.
    • Publish reusable React components for OLGNS integrations.
    • Create a testnet environment or documented testing workflow.
  3. Q2 202703

    Phase 3 — Builder Program

    • Open applications for developer projects.
    • Organize hackathons and technical workshops.
    • Publish contribution guidelines and starter projects.
    • Introduce a transparent grants or bounty program, subject to funding.
    • Encourage independent integrations and open-source contributions.
  4. Q3–Q4 202704

    Phase 4 — Ecosystem Expansion

    • Support third-party applications and integrations.
    • Expand SDKs, APIs, tutorials, and developer tooling.
    • Publish project showcases and contribution records.
    • Explore governance and contribution verification tools.
    • Review ecosystem progress and publish a yearly developer report.
Build tracks

What developers can build

Four areas where OLGNS infrastructure is directly useful to independent builders.

DeFi & Liquidity Tools

Portfolio dashboards, liquidity analytics, pool monitoring, and wallet utilities.

Smart Contract Integrations

Applications using OLGNS contracts, staking interfaces, and verified on-chain reads.

Quantum Security Research

Research prototypes, cryptographic agility, and post-quantum migration experiments — clearly labeled as research until implemented and reviewed.

Open-source Infrastructure

SDKs, documentation, developer APIs, monitoring tools, and community-maintained integrations.

Programs

Developer programs to launch

Each program opens only once its rules, funding and verification process are published.

ProgramPurpose
OLGNS Builder ProgramHelp developers build and showcase applications
OLGNS GrantsFund selected projects through transparent criteria and available funding
Bug BountyEncourage responsible vulnerability reporting
Developer AcademyTutorials, workshops, and starter projects
Open-source ContributionsReward useful documentation, code, testing, and tooling
Ecosystem ShowcasePublish projects with clear descriptions and verification links

Funding principle: eligibility, selection criteria, reward amounts and payment conditions are published before applications are accepted. OLGNS does not promise grants or token rewards that are not funded or approved.

Developer portal structure

Planned navigation for the developer portal at olgns.org/developers.

  • DocumentationPlanned
  • SDKs & APIsPlanned
  • QuickstartPlanned
  • GitHub & Open SourcePlanned
  • Security & Bug BountyPlanned
  • Grants & Builder ProgramPlanned
  • Ecosystem ProjectsPlanned

Developer KPIs

Real activity is tracked instead of vanity metrics. Figures are published only once they can be measured and independently checked.

  • Number of developers who complete a quickstart.
  • Active repositories and external contributors.
  • SDK downloads and API usage, with methodology disclosed.
  • Applications deployed and independently verifiable.
  • Bugs reported and resolved.
  • Grants awarded and deliverables completed.
  • Documentation coverage and update frequency.

Developer program disclaimer

This developer roadmap describes OLGNS planning targets only. Programs, grants, bounties and tooling are published as planned until they are live and independently verifiable. OLGNS does not promise grants or token rewards that are not funded and approved, and eligibility, selection criteria, reward amounts and payment conditions will be published before any applications are accepted.

Reach the OLGNS team on Telegram