martbost
34 lines
13 KiB
HTML
34 lines
13 KiB
HTML
<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><meta name="description" content="How the RM Circle smart contract works — what's locked forever, what the operator can and can't do, and how to verify every claim yourself on the blockchain."><title>Smart Contract Security | RM Circle Team Build</title>
|
|
<link rel="canonical" href="https://rmcircle.team/contract">
|
|
<meta property="og:type" content="website"><meta property="og:site_name" content="RM Circle Team Build"><meta property="og:title" content="How the RM Circle Smart Contract Works — and Why the Bottom Can't Fall Out"><meta property="og:description" content="The code can never change, member money never sits in the contract, and every rule is public. A plain-language review of the verified source — with links to check everything yourself."><meta property="og:image" content="https://rmcircle.team/og-card.jpg"><meta property="og:image:width" content="1200"><meta property="og:image:height" content="630">
|
|
<meta name="twitter:card" content="summary_large_image"><meta name="twitter:title" content="RM Circle Smart Contract — plain-language security review"><meta name="twitter:description" content="What's locked forever, what the operator can and can't do, and how to verify it all yourself."><meta name="twitter:image" content="https://rmcircle.team/og-card.jpg"><link rel="icon" type="image/png" href="/favicon.png"><link rel="stylesheet" href="/styles.css"></head>
|
|
<body>
|
|
<header class="wrap nav"><a class="brand" href="/"><img class="brand-mark" src="/logo.jpg" alt="The RM Circle" width="42" height="42"><span><span id="brandName">RM Circle</span><small>Contract Security</small></span></a><div class="nav-actions"><a class="btn btn-secondary hide-mobile" href="/">← Strategy</a><a class="btn btn-primary" href="/start">Get Started</a></div></header>
|
|
<main>
|
|
<section class="section"><div class="wrap" style="max-width:880px">
|
|
<div class="section-head"><div class="eyebrow">Plain-language code review</div><h1 style="font-size:clamp(32px,5vw,50px);margin:8px 0 10px">Can the bottom fall out of this? <span class="gold">We read the code.</span></h1><p>Every payment in the RM Circle runs through one smart contract on the Polygon blockchain. We reviewed its complete, verified source line by line. Here's what it says — in plain language, with links so you can check every claim yourself. Nobody has to take our word for anything.</p></div>
|
|
|
|
<div class="facts" style="grid-template-columns:repeat(3,1fr);margin:18px 0 26px"><div class="fact"><small>Contract</small><strong style="font-size:13px"><a href="https://polygonscan.com/address/0x33BdAEEfd6d17D80aE53816c916dFb26c4fB2DAF" target="_blank" rel="noopener noreferrer" style="color:var(--teal)">0x33Bd…2DAF ↗</a></strong></div><div class="fact"><small>Network</small><strong>Polygon Mainnet</strong></div><div class="fact"><small>Source verified (Sourcify)</small><strong style="font-size:13px"><a href="https://repo.sourcify.dev/contracts/full_match/137/0x33BdAEEfd6d17D80aE53816c916dFb26c4fB2DAF/" target="_blank" rel="noopener noreferrer" style="color:var(--teal)">Exact match ↗</a></strong></div></div>
|
|
|
|
<div class="card" style="margin-bottom:16px"><h2 style="margin:0 0 10px">1. The code can never change.</h2><p style="color:var(--muted);line-height:1.65;margin:0 0 10px">Some crypto projects use "upgradeable" contracts — the operator can swap in new code after you've joined, changing the rules underneath you. <strong style="color:var(--text)">This contract has none of that machinery.</strong> No proxy, no delegatecall, no self-destruct — the three mechanisms that allow post-launch changes are simply absent from the code. What was deployed on May 27, 2026 is what runs today and what will run in ten years. And because the source is verified as an <em>exact bytecode match</em>, the code we reviewed is provably the code that's running — not a copy, not a claim.</p><p style="color:var(--muted);line-height:1.65;margin:0"><strong style="color:var(--text)">Verified on both major registries.</strong> The source is published and exact-match verified in two independent places: <a href="https://repo.sourcify.dev/contracts/full_match/137/0x33BdAEEfd6d17D80aE53816c916dFb26c4fB2DAF/" target="_blank" rel="noopener noreferrer" style="color:var(--teal)">Sourcify ↗</a> (the open-source registry, verified the day of deployment) and <a href="https://polygonscan.com/address/0x33BdAEEfd6d17D80aE53816c916dFb26c4fB2DAF#code" target="_blank" rel="noopener noreferrer" style="color:var(--teal)">Polygonscan ↗</a> (Exact Match, contract name TRUSTCorona, Solidity 0.8.28). Two registries, independently confirming the same thing: the readable source you can inspect is byte-for-byte the code that's running.</p></div>
|
|
|
|
<div class="card" style="margin-bottom:16px"><h2 style="margin:0 0 10px">2. Member money never sits in the contract.</h2><p style="color:var(--muted);line-height:1.65;margin:0">There is no pool, no vault, no balance an operator could run away with. When someone joins or upgrades, the contract splits and delivers every coin <strong style="color:var(--text)">in the same transaction</strong> — sponsor reward, upline payment, fees — straight to member wallets. If any single transfer fails, the whole transaction reverses and nobody pays anything. You can watch this happen live on the <a href="/#proof" style="color:var(--teal)">payment proof feed</a>: money in, money out, same block.</p></div>
|
|
|
|
<div class="card" style="margin-bottom:16px"><h2 style="margin:0 0 10px">3. The prices and payout rules are locked.</h2><p style="color:var(--muted);line-height:1.65;margin:0">Entry and upgrade costs for all 8 levels were fixed the moment the contract deployed — <strong style="color:var(--text)">there is no function to change them.</strong> The payout split is compiled into the code as constants: on entries, the sponsor receives the slot cost minus a 5% project fee (founders 1% + 1%, development 3%); on upgrades, <strong style="color:var(--text)">100% goes to the eligible upline — the project takes nothing.</strong> There's also no pause switch: nobody can freeze joins, upgrades, or payouts. The eligibility rule is public too: an upgrade payment stops at the first upline who is qualified (2 directs) and already at that level — otherwise it passes them and continues up.</p></div>
|
|
|
|
<div class="card" style="margin-bottom:16px"><h2 style="margin:0 0 10px">4. What the operator CAN do — the honest list.</h2><p style="color:var(--muted);line-height:1.65;margin:0 0 10px">A fair review reports the levers, not just the locks. The contract owner can do exactly four things:</p><ul style="color:var(--muted);line-height:1.7;margin:0;padding-left:20px"><li>Raise or lower the <strong style="color:var(--text)">entry fee percentage</strong> (currently 5%, hard-capped at 50% in the code). This affects the price of <em>future</em> joins only — it can't touch anyone's earnings, and any change is instantly visible on the blockchain.</li><li>Redirect the <strong style="color:var(--text)">project's own fee wallets</strong> (founder/development shares) — their revenue, never member payouts.</li><li>Sweep out coins <strong style="color:var(--text)">accidentally sent</strong> to the contract address — member payment flows never leave a balance behind.</li><li>Transfer ownership of those same limited powers to someone else.</li></ul><p style="color:var(--muted);line-height:1.65;margin:10px 0 0">What the owner <strong style="color:var(--text)">cannot</strong> do: take member funds, change payout rules, change prices, reroute earnings, block withdrawals (there's nothing to withdraw — payments are instant), or replace the code. Even a fully hostile owner is limited to that list above.</p></div>
|
|
|
|
<div class="card" style="margin-bottom:16px"><h2 style="margin:0 0 10px">5. Where "missed" payments go.</h2><p style="color:var(--muted);line-height:1.65;margin:0">When an upgrade payment finds no eligible upline within 16 levels (or reaches the root), it goes to the project's fee wallet rather than vanishing. That's the strongest built-in reason to <strong style="color:var(--text)">get your 2 directs and keep your level current</strong> — eligible positions catch payments; ineligible positions watch them pass by. The <a href="/my" style="color:var(--teal)">Member Dashboard</a> shows exactly this happening in real time.</p></div>
|
|
|
|
<div class="card" style="margin-bottom:16px"><h2 style="margin:0 0 10px">6. What if the creators disappear?</h2><p style="color:var(--muted);line-height:1.65;margin:0 0 10px">A fair question about any on-chain program: if the people who launched it walked away, lost their keys, or simply vanished — does it quietly break over time? For this contract the answer is <strong style="color:var(--text)">no, and we verified it directly on the blockchain</strong> — not just in theory.</p><p style="color:var(--muted);line-height:1.65;margin:0 0 10px"><strong style="color:var(--text)">Nothing needs an admin to keep running.</strong> Joins, upgrades, matrix placement, and every payout are fully automatic. There is no periodic "keepalive," no button anyone has to press to keep payments flowing, and no expiry date anywhere in the code. Whether the creator is present or gone changes nothing about what members receive.</p><p style="color:var(--muted);line-height:1.65;margin:0 0 10px"><strong style="color:var(--text)">A lost or abandoned admin wallet can't jam the machine.</strong> Every payout requires its recipient to accept the coins, so we checked what those admin wallets actually are: the founder, development, and fee-receiver wallets are all <strong style="color:var(--text)">ordinary wallets, not programs.</strong> An ordinary wallet <em>always</em> accepts an incoming payment — even if its key is lost forever and no human is behind it. So even in the worst case, the coins simply arrive and sit there uncollected; the member on the other side of that transaction still gets paid, every time. The only thing that could ever go uncollected is the project's <em>own</em> fee — never a member's earnings.</p><p style="color:var(--muted);line-height:1.65;margin:0">And if the owner's key were lost, the four limited powers from section 4 would simply <strong style="color:var(--text)">freeze in place</strong> forever — the fee percentage and wallet addresses could never change again. Members would never notice, because members never depended on those powers. The contract also keeps <strong style="color:var(--text)">no stored balance</strong> — every payment is delivered in the same transaction it arrives in — so there's nothing sitting inside that could be stranded. In short: this system's survival does not depend on any person staying reachable.</p></div>
|
|
|
|
<div class="card" style="margin-bottom:16px"><h2 style="margin:0 0 10px">Check it yourself — please.</h2><ul style="color:var(--muted);line-height:1.8;margin:0;padding-left:20px"><li><a href="https://polygonscan.com/address/0x33BdAEEfd6d17D80aE53816c916dFb26c4fB2DAF#code" target="_blank" rel="noopener noreferrer" style="color:var(--teal)">The contract on Polygonscan ↗</a> — every transaction, ever, public — now with the verified, readable source under the Contract tab.</li><li><a href="https://repo.sourcify.dev/contracts/full_match/137/0x33BdAEEfd6d17D80aE53816c916dFb26c4fB2DAF/" target="_blank" rel="noopener noreferrer" style="color:var(--teal)">The verified source code ↗</a> — the exact code that's running, independently verified.</li><li><a href="/#proof" style="color:var(--teal)">The live payment feed</a> — every payout on this site links to its blockchain transaction.</li><li>Ask any developer you trust to read the source against this page. It's ~400 lines.</li></ul></div>
|
|
|
|
<div class="callout warning"><strong>What this page is not:</strong> code security is not an income guarantee. This review says the <em>rules can't change underneath you</em> — it does not promise the program grows, that positions fill, or that POL holds its value. Results depend on real participation and duplication, and POL's market price moves. Never use funds you can't afford to lose.</div>
|
|
|
|
<p class="micro" style="margin-top:18px">Review method: complete verified source (Sourcify exact-match, creation + runtime bytecode) read against the deployed contract on 2026-08-13; payout math cross-checked against live on-chain transactions. Reviewed independently by this team's tooling — not by the contract's developers.</p>
|
|
</div></section>
|
|
</main>
|
|
<footer class="wrap disclaimer">This independent team page is educational and is not an earnings guarantee or investment advice. Cryptocurrency and smart-contract participation involve risk, including possible loss of funds. Never use funds you cannot afford to lose.<div class="footer-links"><a href="/">Strategy</a><a href="/start">Getting Started</a><a href="/training">Training</a><a href="/my">Member Dashboard</a><a href="/disclaimer">Disclaimers</a><a href="/how-pay-works">How You Get Paid</a><a href="/tools">Promo Tools</a></div></footer>
|
|
<script src="/track.js"></script><script src="/chat.js" defer></script></body></html>
|