ore.party
Docs
Quick Start Guide
A Party is a group that mines ORE together by minting NFT shares that are an equal claim to the Party's assets. If at any point you need help, join the ORE Discord. To learn more about ORE, go here.
- 1.
- 2.
Create a Party, or mint into one. Guides on how to do each can be found in the next two sections.
- 3.
The SOL from minting funds mining for the Party. A mint is open 72 hours, until all NFTs are minted, or until at least 50% of NFTs are minted and the Founder ends the mint. If at least 50% of NFTs are not minted after 72 hours, everyone is refunded minus mint fees.
- 4.
3% of mint fees buy GRAMS for the Party. GRAMS earn stORE (ORE's liquid staking token) for the Party just by holding. Learn more about GRAMS.
- 5.
The Party starts mining ORE automatically. Wins pay Unrefined ORE into the Party coffers. Each NFT has an equal claim to its share of the Party assets.
- 6.
By holding Unrefined ORE, the Party automatically earns Refined ORE. The current APR is …!
- 7.
When mining ends, you can burn your NFT to claim your proportional share of the Party's assets if so desired. When you burn, you pay a 1.5% fee to the Party so holders earn more. You don't have to burn, you can hold and keep earning Refined ORE and stORE as long as you want.
- 8.
Once an NFT's Refined ORE reaches 2.5% of its Unrefined ORE, it can be listed for sale in the marketplace. When purchased, the new owner receives the NFT and the right to its share of the Party assets.
- 9.
When all other NFTs in a Party are burned, you are the Last Standing NFT. Once the Party has 0.1 Refined ORE, your NFT becomes eligible for withdrawal. It is also added automatically to the ORE Party Collection. You can list your ORE Party Collection for sale in the Collection area of the site or continue to hold it. The NFT and Party continue to earn yield from ORE and GRAMS until it is finally burned.
- 10.
Founders can be followed by clicking on the Star next to their username. When you follow a Founder, you are messaged any time they start a new Party.
How to Mint an NFT
Minting an NFT with SOL buys an equal share of a Party's assets. You can mint from a Party card on the home page, or from the Party's page.
- 1.
On the home page, pick a Party that still has remaining NFTS. The card shows vault SOL, ORE, GRAMS, and a line like 5 minted · 15 remaining.
- 2.
Hover over the pickaxe icon to see the Party's mining strategy.

- 3.
To mint, click the gold Mint bar. The price per NFT is in SOL. Use − / + to buy 1–5 NFTS in one transaction.
- 4.
When you mint, the following is how the SOL is used:
- 96.25% SOL to mining coffers — this will be used to mine ORE on behalf of the Party.
- 3% GRAMS to Party coffers — 3% of the SOL is used to buy GRAMS for the Party. GRAMS earns the Party ORE just for holding. If and when you burn your NFT, you receive GRAMS in addition to the ORE.
- 0.50% SOL to ORE.party Treasury — This helps keep this site running.
- 0.25% GRAMS to ORE Vault — This is locked away forever and the ORE it earns is buried, benefiting the ORE Protocol.
- 5.
Once you successfully mint, you now own part of the Party. You can see the list of Parties you're a part of (and much more) in the Vault.
- 6.
A Party will start mining once all the NFTs are minted, after 72 hours as long as 50%+ of the NFTs are minted, or if the Founder ends the mint early as long as 50%+ of the NFTs are minted. If less than 50% are minted, you will be refunded your SOL minus the fees above.
How to create a Party
You can easily create a Party, become a Founder, and earn 0.5% of Party Member's NFT value when they burn. Make a name for yourself by creating lucrative Parties and people will find and follow you via the stats section of the site.
- 1.
Click on "Create" at the top of your screen and name your Party.
- 2.
In the Charter section, describe your Party's strategy or what makes you unique.
- 3.
NFT — upload a square image, or pick a unique premade plate. Length must be the same on all sides.
- 4.
Choose the Supply wisely. Remember, your Party must mint at least 50% of its NFTs within 72 hours or everyone will be refunded.
- 5.
Select a mint price. The more SOL and Supply, the more your Party can mine with. But be careful about going too high and your Party not minting at least 50% of its NFTs and being refunded.
- 6.
Under Mining Strategy, choose Lite Mode or Pro Mode. Details on each are below.
Lite Mode
Lite Mode uses ORE.com's autominer. It deploys every round until leftover SOL cannot fund another deploy at which point the dust SOL is converted to GRAMS for the Party. Mining cannot be stopped. These are the Lite Mode variables:
- Solo tiles (0–10) — there are 10 solo tiles on the ORE.com grid. If one is selected, a single winner is awarded the ORE. Odds of winning depend upon how much SOL you deployed. As such, if the amount of SOL you deploy per round is low, we recommend using the split tiles detailed below.
- Split tiles (0–15) — there are 15 split tiles. If one is selected, everyone on that tile is awarded ORE in proportion to the SOL they deployed. Default is 15 split tiles and 0 solo tiles.
- Rounds (25–10,000, default 250) — how many mining rounds your Party's SOL is spread across. SOL per round is the Party's total SOL divided by these rounds. If your Party does not fully mint, you choose what changes when mining starts: by default the rounds stay the same and SOL per round is reset to the actual vaulted amount, or SOL per round stays the same and your Party mines fewer rounds. More rounds spend less per round and last longer. Note that the actual number of rounds your Miner deploys on will be far higher than this because you receive SOL back from tiles that aren't chosen which is redeployed.
- Min motherlode (0–1,000 ORE) — The Miner will skip a round when the Motherlode is below this. In other words, if you select 10, the Miner won't start mining until the Motherlode is 10 ORE or higher. 0 means no floor.
- Max motherlode (0–1,000 ORE, or infinity) — The Miner will skip a round when the Motherlode is above this. In other words, if you select 10, the Miner will stop mining after the Motherlode hits 10 and won't start again until the Motherlode is hit. Infinity means no ceiling.
- As you change variables, the form will show the amount of SOL per tile and SOL per round.
Pro Mode
Pro Mode uses the ORE Party deploy bot. It deploys late in each round, and only when your conditions are met. Set the same Lite Mode tile, round, and motherlode fields first, then the Deploy bot options:
- Seconds left (0.2–12, default 0.6) — the bot deploys when this many seconds are left before the ORE.com round closes. Time moves in Solana slots of about 0.2 seconds each, so the value steps by 0.2. Later deploys see more of the board, but leave less time to land. A deploy that does not land is not charged SOL.
- SOL per tile — Fixed or Share. Fixed (the default) puts the same amount on every tile. Share puts a percentage of the SOL already on each tile, never more than the per-tile amount and at least 0.00001 SOL. A basis point (bp) is 1/100 of a percent: the default 50 bps is 0.5%. For an in-depth explanation, go to the SOL per tile section of these docs.
- Minimum Discount (%) — deploy only when ORE costs at least this much less to produce than it sells for. Off, the default, never skips a round for price. Range is 0–90. See Minimum Discount later in these docs.
- Count Motherlode — only shows when you enable the Minimum Discount. When on, the cost uses the Motherlode's expected payout this round: ORE pays the whole pool in about 1 of every 500 rounds, so the cost is divided by 1 ORE plus the current pool divided by 500. This Motherlode adjustment is the same for every Party and does not depend on how much SOL you deploy. A pool above 100 ORE makes ORE cheaper to produce, a pool below 100 ORE makes it more expensive, and at 100 ORE it matches Off. Off uses the usual 1.2 ORE per round.
SOL per tile
On a Pro Party, SOL per tile sets how much SOL the deploy bot puts on each tile it picks in a round. The tile counts are set separately. Choose Fixed or Share when you create the Party.
Fixed (the default): every tile gets the same amount, the per-tile amount shown under the Pro options. For example, 15 tiles at 0.002567 SOL each cost 0.0385 SOL every round, so the cost is predictable.
Share: each tile gets a percentage of the SOL other players have already put on it. Choosing Share adds a Tile share (bps) setting. A basis point (bp) is 1/100 of a percent: the default 50 bps is 0.5%, and you can set 1 bp to 100% in steps of 5. Example with 50 bps (0.5%) and a per-tile amount of 0.002567 SOL:
| SOL already on the tile | 0.5% of it | What the bot deploys |
|---|---|---|
| 0.1 SOL | 0.0005 | 0.0005 SOL |
| 0.4 SOL | 0.002 | 0.002 SOL |
| 2 SOL | 0.01 | 0.002567 SOL (capped at the per-tile amount) |
| Almost empty | Tiny | 0.00001 SOL (the minimum) |
- Never more than the per-tile amount. The Fixed amount is the ceiling, so Share never costs more per round than Fixed.
- At least 0.00001 SOL per tile, so a near-empty tile still gets a valid deploy.
- Rounded down to two significant figures, then grouped into at most 8 different amounts, so the whole round fits in one transaction.
Which to choose: on ORE, a winning tile pays out by your share of that tile’s SOL. Fixed puts the same amount everywhere, so you hold a big share of quiet tiles and a small share of crowded ones. Share keeps your share of each tile about the same, spending less on quiet tiles and more on busy ones, up to the per-tile amount. A Share round usually costs less than Fixed, and its cost changes with how crowded the board is.
The bot sizes each tile in the last moments of the round (Seconds left, 0.6 by default), so it sees almost every other deploy first. New to Pro? Start with Fixed: its cost per round is easy to check.
Minimum Discount
On a Pro Party, Minimum Discount decides which rounds are worth mining. Just before it deploys, the deploy bot estimates what one ORE will cost to produce this round and compares it with what ORE sells for right now. It deploys only when the cost is at least your discount below that price. Off, the default, never skips a round for price.
The cost: after a 1% admin fee, ORE keeps 10% of the SOL on every tile except the winning one. With 24 of the 25 tiles losing, that averages about 9.5% of the SOL on the board, counting the Party’s own deploy. ORE mints 1.2 ORE per round (1 ORE to the winners and 0.2 ORE into the Motherlode), so each ORE costs about 0.079 times the SOL on the board. With Count Motherlode on, 1 ORE plus the pool divided by 500 replaces the 1.2. The price: what selling 1 ORE on Jupiter pays right now. Both are in SOL, so moves in the dollar prices of SOL and ORE are already counted.
The rule: deploy only if cost ≤ (100% − discount) × price. Examples with a 20% discount, so the cost must be at most 80% of the price:
| ORE price | Board after your deploy | Cost per ORE | Result |
|---|---|---|---|
| 0.99 SOL | 9.8 SOL | 0.78 SOL | Deploys |
| 0.99 SOL | 10.3 SOL | 0.82 SOL | Skips: above 0.79 |
| 1.20 SOL | 11.5 SOL | 0.91 SOL | Deploys: ORE rose, so the same board is a better deal |
| 0.80 SOL | 9.0 SOL | 0.71 SOL | Skips: above 0.64 |
| No price | Any | Any | Waits, then skips if none arrives before the round closes |
- The price is a live Jupiter quote, refreshed every 15 seconds and never used once it is over 60 seconds old. With no fresh price, the bot keeps trying until the round closes and skips it only if no price arrives. It never guesses a price.
- The bot checks just before it deploys. SOL other players add after that is not counted, so a smaller Seconds left leaves less room for surprises.
- This is ORE’s production cost for the whole board, not a forecast of your Party’s profit. It leaves out the 1% admin fee on every tile and the executor fee, which your Party also pays. Adding the admin fee to the same board-wide calculation raises the figure by about 10%, before the executor fee. A quieter tile earns more ORE per SOL deployed, so the bot’s choice of the least crowded tiles works in your Party’s favor.
- When you create a Party, the estimate under Minimum Discount adds your tiles and per-tile SOL to the final board of each recent round and works out the cost the same way the bot does. It shows the median cost of the last 5 finished rounds and how many of the last 100 rounds' final boards would have passed the rule at the current price and Motherlode. It also says when your Motherlode limits stop the bot right now. It describes recent rounds: the bot still decides each round from the live board shortly before the round ends.
Fees
ORE.party does not custody miner tokens. Party vaults (program PDAs) hold a Party’s SOL, Unrefined ORE, Refined ORE, $GRAMS, and stORE.
| Action | What you pay | Where it goes |
|---|---|---|
| Mint a Party NFT | Listed mint price in SOL | 96.25% SOL to mining coffers · 3% GRAMS to Party coffers · 0.50% SOL to ORE.party Treasury · 0.25% GRAMS to ORE Vault · no Founder cut |
| Burn / claim | Your NFT | Claim your share of Unrefined + Refined + Party GRAMS + stORE. 10% of Unrefined is a refining tax to miners who have not claimed. Then 1.5% Party, 0.5% Party Founder, 0.5% Ore Party Treasury. The last NFT still pays the refining tax and 0.5% treasury; Party 1.5% and Founder 0.5% are waived. |
GRAMS & stORE
GRAMS is an ORE-paired memecoin that pays ORE to holders. On ORE Party it is the only mint pair. Mint cuts buy GRAMS for Party coffers and the ORE Vault. Anyone can also send GRAMS to the vault address under the Party name.
- The ORE Party contract wraps GRAMS-reward ORE into stORE, ORE’s liquid staking token, so that ORE keeps working.
- A Party needs at least $20 of GRAMS held to receive stORE drops.
- 0.25% of each mint is bought as GRAMS for the ORE Vault at grams.supply/vault. Tokens sent there are locked.
- Other Assets on a Party show GRAMS held (and its dollar value) and stORE from GRAMS (and its dollar value).
Parties & NFTs
A Party is a mining crew with a capped NFT supply. Each NFT is an equal share of Party assets. Mint proceeds buy mining SOL, GRAMS for the Party coffers, and GRAMS for the ORE Vault. Nothing from mint goes to the Party Founder.
- Party names are 2–21 characters.
- Mint price is 0.05–50 SOL. Below 0.05 SOL the vault cannot open the ORE.com autominer.
- Mint up to 5 NFTs at once with the number picker on the mint button. They mint in one transaction, so you get all of them or none. If someone mints first, the transaction mints nothing and you can try again.
- Upload a square NFT when you create a Party, or use a template.
- Mint stays open 72 hours. A Party needs at least 50% of its NFTS minted (both for a 2-NFT Party) to mine, and the Founder can end the mint only after that. If the window closes at or above it, leftover NFTS are deleted and mining starts. If it closes below, every minter is refunded 96.25% of their mint SOL (the 3.75% mint fee is kept), Orelana messages them, and the Party leaves the front page.
- Choose 25–10,000 mining rounds (default 250). SOL per round is the expected 96.25% mine take divided by those rounds, then reset to the actual vault when mining starts.
- Default deploy is 15 split tiles and 0 solo tiles. A thin solo-tile deploy warns once.
- The vault address sits under the Party name. Copy it to send GRAMS (or SOL before automation starts).
- Burning all of a Founder’s NFTs does not dissolve the Party.
- Private Parties still mint on-chain; after minting ends only the NFT, name, and total assets are public.
- A Party page has Party, Your Share, Member List, and Mining Log.
- The last unburned NFT can be withdrawn as a Metaplex Core NFT in the official ORE Party collection. The program mints it with a fixed name and metadata link; the holder cannot rename it, swap the metadata, or add a transfer/burn delegate. The Party stays open and keeps accruing rewards. Whoever holds that NFT owns the Party, including after a wallet transfer or a Magic Eden sale. Burning it on ORE Party claims the vault; copies that are not the bound Core NFT cannot.
Marketplace
The Marketplace is where you buy and sell ORE Party NFTs for SOL. It lists every NFT for sale, plus a Sales History of past sales. A purchase moves the NFT to the buyer. They then have claim to its share of the Party assets, and they can list it again.
Listing
You can list your NFT via your Vault or from a Party page once mining is complete. Change the terms or delist at any time. A listed NFT cannot be burned until you delist it but does continue to earn yield.
- The Party must be done mining and the NFT's Refined ORE must reach 2.5% of its Unrefined ORE before it can be listed (an NFT with 100 ORE needs 2.5 Refined ORE).
- ORE Party Collection NFTs (the Party's last unburned NFT that lays claim to at least 0.10 Refined ORE) can be listed. While listed it sits in the ORE Party escrow.
Pricing
Asset value is what burning the NFT would pay you today: its equal share of Unrefined ORE, Refined ORE, GRAMS, and stORE, after the refining tax, burn fees, and the GRAMS transfer fee, priced in SOL. Pick one way to price the listing:
- % Above value -- this keeps the price up to your set % above asset value. The system automatically adjusts the price at regular intervals.
- % Below value -- this keeps the price at your specified % below asset value.
- Fixed price in SOL. It changes only when you update the listing.
A buy is quoted from live SOL and ORE prices and holds for about a minute. If prices move, get a new quote. The buyer pays the quoted SOL from their connected wallet.
Sale fees
Fees are paid by the seller. After fees are removed, the seller's wallet receives the rest.
- 0.25% is bought as GRAMS for the Party.
- 0.5% goes to the ORE Party Treasury.
- 0.25% is bought as GRAMS for the ORE Vault.
- 3.5% is bought as jitoSOL for the ORE Reserve.
When sales pause
Occasionally sales in the marketplace will be paused due to ORE and/or SOL price discrepancies. This usually lasts only a few minutes.
Mining
Each Party mines on ORE.com with SOL from its autominer. Wins land in the Party as Unrefined ORE (and sometimes a Motherlode). The keeper closes an expired mint on-chain and starts the autominer when minting ends. Leftover SOL auto-reloads each round until it cannot fund another deploy.
- Status is Mining while the autominer can still fund its per-square amount times the Party’s tiles.
- Status is Mining Complete when leftover SOL cannot fund that deploy, the autominer closed after it had already spent, or the Party is Claimable on-chain. A round that is still settling is never counted short: the check waits for its checkpoint, which reloads the round’s returned SOL. Whatever SOL is left when mining ends is converted to GRAMS for the Party.
- SOL sent to the vault before Start Automation is mined. SOL sent after automation exists sits unused. Adding SOL after mining stops does not start it again.
- Mining Log lists live ORE.com rounds. SOL deployed is this Party’s per-square amount times its tiles, not another miner in the same bundled transaction. Your Share is your cut of that round’s ORE, split equally by the NFTs of the Party you hold now. Sign in to see it.
- The first Random round deploys to consecutive squares starting at square zero, not the solo/split kinds. A Party with no split tiles can still take a Split share on that round. Later rounds follow the tile counts.
- When mining starts — the mint sold out, the 72-hour window ended, or the Founder ended the mint — Orelana messages every NFT holder.
- When mining is complete, Orelana messages every NFT holder to hold for Refined ORE yield or burn to claim Party assets.
- When the second-to-last NFT is burned, Orelana messages whoever holds the final NFT.
Vault & Collection
Vault is your claim, the Parties you hold, Parties you founded, and a CSV transaction log. Burn after mining ends to claim your slice in your wallet.
- Burn to claim Unrefined, Refined, Party GRAMS, and stORE.
- Your claim shows an APR on Refined ORE and stORE after each dollar value. Refined ORE sums the refining fees paid over the last 7 days, divides by the current unrefined pool, and annualizes that rate. stORE is calculated independently from its own last 7 days.
- Hold Unrefined to earn Refined from other miners’ 10% claim tax.
- The last NFT still pays the refining tax and 0.5% treasury; Party and Founder fees are waived.
- The Collection lists the last unburned NFT of a Party when that NFT’s claim is at least 0.10 Refined ORE, ranked by dollar value. Burning it removes it.
- Withdraw the last NFT to a wallet, then list it for sale in SOL from your Vault. While listed it sits in ORE Party escrow, shows its price on The Collection, and cannot be burned; delist any time to take it back. A sale pays a 2.5% fee to the ORE Party Treasury and nothing else. The site follows custody of that Core NFT when you connect.
API
ORE Party has a free, public, read-only API for bots, dashboards, and alerts — for example, a Discord bot that pings members when their Party hits a SOLO or the Motherlode. There is no API key and no sign-in: send a GET request and get JSON back.
- Base URL:
https://ore.party. Every endpoint is aGETrequest and returns JSON. - Requests from any website or server are allowed (CORS is open).
- The data is what ORE Party has already stored from the chain, refreshed about every 5 minutes, so it can trail ORE.com by a few minutes. Responses are cached for 30–60 seconds, so polling more than once a minute gains nothing.
- Amounts come twice: in raw units and as decimals. SOL is counted in lamports (
solLamports; 1 SOL = 1,000,000,000 lamports) and ORE in grams (oreWonGrams; 1 ORE = 100,000,000,000 grams). Use the raw values for math. - Private Parties show only their name, link, and status. Their addresses, assets, mining strategy, and Mining Log come back as
null, just as their page hides them from anyone who doesn't hold one of their NFTs. - Usernames can change, and a username someone gives up can be taken by someone else. Look each person up by username once, then follow them by their permanent
userId(see the next section). - An unknown username or Party returns HTTP
404with a body like{"error": "Unknown user."}. - Each IP address can make up to 120 requests a minute across all servers. Past that you get HTTP
429; itsRetry-Afterheader says how many seconds to wait. An unlisted, repeated, or invalid query parameter returns HTTP400.
Get a user's Parties
GET /api/users/{username}/parties lists every Party the user holds at least one NFT in. Use the username shown on their ORE Party profile; capitalization doesn't matter.
curl https://ore.party/api/users/wildming/parties
{
"username": "WildMing",
"userId": "3c9Jt1Qk7Wn2Lx5Rv8Hb0Zf4",
"userApiUrl": "https://ore.party/api/users/by-id/3c9Jt1Qk7Wn2Lx5Rv8Hb0Zf4/parties",
"wallet": "7xKXtg2CW87d97TXJSDpbD5jBkheTqA83TZRuJosgAsU",
"parties": [
{
"name": "Gold Rush",
"slug": "gold-rush",
"url": "https://ore.party/gold-rush",
"private": false,
"nftsOwned": 2,
"status": "mining",
"party": "9xQeWvG816bUx9EPjHmaT23yvVM2ZWbrrpZb9PusVFin",
"vault": "HCoVAT34F2LAXDiJcTGwhidiWPzCDPA6yVCXndJWBH4H",
"miningPda": "KhGJG2e6hiUGSHRkFi8X1Jmc7e94R8ARCaDjsNbGJtt",
"assets": {
"solLamports": 1234500000,
"sol": 1.2345,
"unrefinedOreGrams": 300000000000,
"unrefinedOre": 3,
"refinedOreGrams": 50000000000,
"refinedOre": 0.5
},
"miningApiUrl": "https://ore.party/api/parties/KhGJG2e6hiUGSHRkFi8X1Jmc7e94R8ARCaDjsNbGJtt/mining"
},
{
"name": "Night Shift",
"slug": "night-shift",
"url": "https://ore.party/night-shift",
"private": true,
"nftsOwned": 1,
"status": "mining",
"party": null,
"vault": null,
"miningPda": null,
"assets": null,
"miningApiUrl": null
}
]
}Once you have someone's userId, use GET /api/users/by-id/{userId}/parties instead. It returns the same response and keeps working after they change their username. Every response includes this link, ready to store, as userApiUrl.
curl https://ore.party/api/users/by-id/3c9Jt1Qk7Wn2Lx5Rv8Hb0Zf4/partiesusername- The username as the user wrote it, or
nullif they haven't chosen one. It can change at any time, so don't use it to recognize someone. userId,wallet- The user's permanent ID, which never changes, and their linked Solana wallet (
walletisnullif none is linked). userApiUrl- This user's Parties by
userId. Store it and call it from then on. parties[].name,slug,url- The Party's name, its short name, and its page on ORE Party.
parties[].privatetruefor a private Party (see above).parties[].nftsOwned- How many of the Party's NFTs this user holds.
parties[].statusminting,mining,complete(Mining Complete),dissolved,refunding, orrefunded.parties[].party,vault- The Party's on-chain account, and the vault that holds its assets.
parties[].miningPda- The Party's ORE miner account on ORE.com. Look it up on any Solana explorer to see the Party's deploys.
parties[].assets- Mining assets: the same numbers as the Party's Mining Assets panel (see the next endpoint).
parties[].miningApiUrl- A ready-made link to this Party's mining endpoint.
nullwhile the Party isn't on-chain yet, or when it's private.
Get a Party's mining status, assets, strategy, and Mining Log
GET /api/parties/{id}/mining tells you whether a Party is mining, what it has left, how it mines, and what its Mining Log says. {id} can be the Party's miningPda, its party address, or its slug. Add ?limit= to choose how many recent rounds come back: 1–100, default 25.
curl "https://ore.party/api/parties/KhGJG2e6hiUGSHRkFi8X1Jmc7e94R8ARCaDjsNbGJtt/mining?limit=2"
{
"name": "Gold Rush",
"slug": "gold-rush",
"url": "https://ore.party/gold-rush",
"private": false,
"status": "mining",
"party": "9xQeWvG816bUx9EPjHmaT23yvVM2ZWbrrpZb9PusVFin",
"vault": "HCoVAT34F2LAXDiJcTGwhidiWPzCDPA6yVCXndJWBH4H",
"miningPda": "KhGJG2e6hiUGSHRkFi8X1Jmc7e94R8ARCaDjsNbGJtt",
"assets": {
"solLamports": 1234500000,
"sol": 1.2345,
"unrefinedOreGrams": 300000000000,
"unrefinedOre": 3,
"refinedOreGrams": 50000000000,
"refinedOre": 0.5,
"recentAvgDeployLamports": 50000000
},
"strategy": {
"mode": "pro",
"soloTiles": 0,
"splitTiles": 15,
"rounds": 250,
"solPerRoundLamports": 38500000,
"solPerRound": 0.0385,
"solPerTileLamports": 2566667,
"solPerTile": 0.002566667,
"minMotherlodeOre": 0,
"maxMotherlodeOre": null,
"keepSolPerRound": false,
"pro": {
"secondsLeft": 0.6,
"slotsLeft": 3,
"solPerTileMode": "share",
"tileShareBps": 50,
"minDiscountPct": 20,
"countMotherlode": false,
"maxCostSolPerOre": null,
"technicals": false
}
},
"nftsOutstanding": 4,
"holders": [
{
"userId": "3c9Jt1Qk7Wn2Lx5Rv8Hb0Zf4",
"username": "WildMing",
"wallet": "7xKXtg2CW87d97TXJSDpbD5jBkheTqA83TZRuJosgAsU",
"nftsOwned": 3,
"userApiUrl": "https://ore.party/api/users/by-id/3c9Jt1Qk7Wn2Lx5Rv8Hb0Zf4/parties"
},
{
"userId": "8pQw2Ze5Ty7Ui9Op1As3Df6G",
"username": "SolStacker",
"wallet": "5yNmR8sVqW2tX4uZ6aB8cD1eF3gH5jK7mN9pQ2rS4tUv",
"nftsOwned": 1,
"userApiUrl": "https://ore.party/api/users/by-id/8pQw2Ze5Ty7Ui9Op1As3Df6G/parties"
}
],
"miningLog": {
"totalRounds": 412,
"storedRounds": 412,
"historyComplete": true,
"scannedAt": "2026-10-08T16:05:12.000Z",
"wins": 31,
"soloWins": 2,
"motherlodeWins": 1,
"oreWonGrams": 1310000000000,
"oreWon": 13.1,
"lastSoloWin": {
"roundId": 98120,
"signature": "4sGjMW1sTnyUYwM5vBRt8TQq3PXTwZ2w9hRZk2kYdC9xVz6Fq1bE7pW1rZ5uH3cN2sJ8yL4mK6dA9fT1gB3hQ7e",
"solDeployedLamports": 50000000,
"solDeployed": 0.05,
"squares": [1, 2, 3, 4, 5],
"winningSquare": 3,
"tileKind": "solo",
"pending": false,
"oreWonGrams": 100000000000,
"oreWon": 1,
"won": true,
"solo": true,
"motherlodePaid": false,
"motherlodeGrams": 0,
"wonMotherlode": false,
"shares": [
{
"userId": "3c9Jt1Qk7Wn2Lx5Rv8Hb0Zf4",
"username": "WildMing",
"wallet": "7xKXtg2CW87d97TXJSDpbD5jBkheTqA83TZRuJosgAsU",
"nftsOwned": 3,
"oreWonGrams": 75000000000,
"oreWon": 0.75
},
{
"userId": "8pQw2Ze5Ty7Ui9Op1As3Df6G",
"username": "SolStacker",
"wallet": "5yNmR8sVqW2tX4uZ6aB8cD1eF3gH5jK7mN9pQ2rS4tUv",
"nftsOwned": 1,
"oreWonGrams": 25000000000,
"oreWon": 0.25
}
]
},
"lastMotherlodeWin": {
"roundId": 98377,
"signature": "2Hk9vQx3Rz7LmN5pT8wY1cF4bJ6dS0aE3gK7uV9iO2qW5eR8tY1uI4oP7aS0dF3gH6jK9lZ2xC5vB8nM1qW4eR",
"solDeployedLamports": 50000000,
"solDeployed": 0.05,
"squares": [1, 2, 3, 4, 5],
"winningSquare": 3,
"tileKind": "split",
"pending": false,
"oreWonGrams": 1200000000000,
"oreWon": 12,
"won": true,
"solo": false,
"motherlodePaid": true,
"motherlodeGrams": 4000000000000,
"wonMotherlode": true,
"shares": [
{
"userId": "3c9Jt1Qk7Wn2Lx5Rv8Hb0Zf4",
"username": "WildMing",
"wallet": "7xKXtg2CW87d97TXJSDpbD5jBkheTqA83TZRuJosgAsU",
"nftsOwned": 3,
"oreWonGrams": 900000000000,
"oreWon": 9
},
{
"userId": "8pQw2Ze5Ty7Ui9Op1As3Df6G",
"username": "SolStacker",
"wallet": "5yNmR8sVqW2tX4uZ6aB8cD1eF3gH5jK7mN9pQ2rS4tUv",
"nftsOwned": 1,
"oreWonGrams": 300000000000,
"oreWon": 3
}
]
},
"rows": [
{
"roundId": 98402,
"signature": "5tRe8wQ2yU4iO6pA1sD3fG5hJ7kL9zX2cV4bN6mQ8wE1rT3yU5iO7pA9sD2fG4hJ6kL8zX1cV3bN5mQ7wE9rT",
"solDeployedLamports": 50000000,
"solDeployed": 0.05,
"squares": [1, 2, 3, 4, 5],
"winningSquare": null,
"tileKind": null,
"pending": true,
"oreWonGrams": 0,
"oreWon": 0,
"won": false,
"solo": false,
"motherlodePaid": false,
"motherlodeGrams": 0,
"wonMotherlode": false,
"shares": null
},
{
"roundId": 98401,
"signature": "3pL7kJ5hG3fD1sA9qW7eR5tY3uI1oP9aS7dF5gH3jK1lZ9xC7vB5nM3qW1eR9tY7uI5oP3aS1dF9gH7jK5lZ3x",
"solDeployedLamports": 50000000,
"solDeployed": 0.05,
"squares": [1, 2, 3, 4, 5],
"winningSquare": 17,
"tileKind": "split",
"pending": false,
"oreWonGrams": 0,
"oreWon": 0,
"won": false,
"solo": false,
"motherlodePaid": false,
"motherlodeGrams": 0,
"wonMotherlode": false,
"shares": null
}
]
}
}status- Is it mining?
miningmeans the autominer is still deploying.completemeans mining is over, and holders can burn or keep earning Refined ORE. assets.sol,solLamports- What's left: the SOL the Party still has to mine with (its autominer balance once mining starts).
assets.unrefinedOre,refinedOre- Unrefined and Refined ORE held by the Party.
assets.recentAvgDeployLamports- Average SOL deployed per round over the latest rounds. Divide
solLamportsby it for a rough count of rounds left. nftsOutstanding- NFTs not yet burned. Each one is an equal share of the Party, so a holder's share is their
nftsOwneddivided by this. holders- Everyone holding the Party's NFTs, the same people as its Member List, most NFTs first:
userId,username,wallet,nftsOwned, anduserApiUrl. An NFT withdrawn to a wallet that isn't linked to an ORE Party account shows only itswallet, withuserId,username, anduserApiUrlset tonull. miningLog.totalRounds,storedRounds- Rounds the Party has deployed on, and how many of them ORE Party has stored so far.
miningLog.historyCompletetrueonce every round since the first deploy is stored, so the win counts are lifetime totals.miningLog.scannedAt- When the log was last refreshed from the chain.
miningLog.wins,soloWins,motherlodeWins- Settled rounds where the Party won ORE, won a SOLO, and won a share of the Motherlode.
miningLog.oreWon- Total ORE won across those rounds.
miningLog.lastSoloWin,lastMotherlodeWin- The most recent SOLO win and Motherlode win, each a full round (fields below), or
nullif there hasn't been one. miningLog.rows- The latest rounds, newest first.
strategy is the Party's Mining settings, the same ones its page shows. It comes back while the Party is still minting too, so you can see how a Party will mine before you mint.
strategy.modelite(ORE.com's autominer) orpro(the ORE Party deploy bot). See Lite Mode and Pro Mode earlier in these docs.strategy.soloTiles,splitTiles- How many solo tiles (0–10) and split tiles (0–15) the Party deploys on each round.
strategy.rounds- How many rounds the Party's SOL is spread across (25–10,000).
strategy.solPerRound,solPerTile- Configured SOL per round and per tile. For Lite and Pro
fixed, these are the deploy amounts. For Proshare, they are maximums: actual spending depends on the SOL already on each tile and can be lower. Set from the expected mint when the Party is created, then reset to the SOL actually in the vault when mining starts. strategy.keepSolPerRound- What the Founder chose for a Party that does not fully mint.
false(the default) keeps the rounds and lowers SOL per round when mining starts;truekeeps SOL per round and mines fewer rounds. strategy.minMotherlodeOre,maxMotherlodeOre- The Party skips a round when the Motherlode is below the minimum or above the maximum.
0means no floor, andnullmeans no ceiling. strategy.pro- The Pro options below, or
nullfor a Lite Party. pro.secondsLeft,slotsLeft- The deploy bot deploys when this many seconds are left in the round. Time moves in Solana slots of about 0.2 seconds each.
pro.solPerTileMode,tileShareBpsfixedputs the same amount on every tile.shareputstileShareBpsbasis points of the SOL already on each tile, never more thansolPerTile.tileShareBpsisnullforfixed.pro.minDiscountPct,countMotherlode- Minimum Discount: deploy only when ORE costs at least this % less to produce than it sells for, counting the Motherlode when
countMotherlodeistrue.nullmeans Off. pro.maxCostSolPerOre- A fixed cost cap in SOL per ORE, used only by Parties created before Minimum Discount. Otherwise
null. pro.technicalstruewhen Technical Indicators is set to Below 200 day SMA: the deploy bot also waits until ORE's USD price is below its 200-day simple moving average.
roundId,signature- The ORE.com round, and the deploy transaction (look it up on any Solana explorer).
solDeployed- SOL the Party deployed that round.
squares,winningSquare- The squares the Party deployed on (0–24), and the square that won.
tileKindsoloif one miner took the round's ORE,splitif everyone on the winning tile shared it.pendingtrueuntil the round settles. Pending rounds never count as wins; check again later.oreWon,won- ORE the Party won that round, Motherlode share included, and whether it won any.
solotrueonly when the Party itself took a Solo round's ORE as its one winning miner. This is a SOLO. A Solo round that also paid the Motherlode gives every miner on the winning tile a Motherlode share, so a row can havetileKindsoloand ORE won whilesoloisfalse.motherlodePaid,motherlodeGrams- Whether the Motherlode paid out this round (the Mining Log's ML Hit column), and how big it was.
wonMotherlodetruewhen the Party won ORE on a round that paid the Motherlode, so it got a share. This is an ML.shares- Each holder's share of the ORE on a SOLO or ML round (
soloorwonMotherlodeistrue), ornullon every other round. See below.
To get each member's share of a SOLO or ML, read shares on miningLog.lastSoloWin, lastMotherlodeWin, or any row where solo or wonMotherlode is true. It has one entry per holder with their userId, username, wallet, nftsOwned, and oreWon (oreWonGrams in raw units): the round's oreWon divided by nftsOutstanding, times nftsOwned, rounded down to the gram. That is the same number as the Mining Log's Your Share column. The ORE stays in the Party, so shares follow whoever holds the NFTs now, not who held them during the round. To find one member, match shares[].userId to the userId you saved for them.
Example: SOLO and Motherlode alerts
- 1.
Ask each member for their ORE Party username once, call the user endpoint with it, and save the
userApiUrlit returns. - 2.
From then on, check each member with their
userApiUrl, never their username. A rename won't break the link, and a username someone gives up won't point you at a different person. - 3.
Every few minutes, call each Party's
miningApiUrl. A Party needs only one call, however many of your members are in it. - 4.
Remember
lastSoloWin.roundIdandlastMotherlodeWin.roundIdfor eachminingPda. When either goes up, post an alert, with each member's cut from that round'sshares. - 5.
When
statuschanges fromminingtocomplete, tell the holders mining is over. - 6.
Refresh each member's Party list now and then (daily is plenty) to pick up Parties they join or leave.
// Node 18+ or any browser. Checks members' Parties every 5 minutes
// and posts new SOLO and Motherlode wins.
const BASE = "https://ore.party";
// Load these saved member ID -> userApiUrl pairs from your database or config.
// Unlike a username, a saved userApiUrl still identifies the same account after a restart.
const members = new Map([
["discord-member-1", "https://ore.party/api/users/by-id/3c9Jt1Qk7Wn2Lx5Rv8Hb0Zf4/parties"],
]);
const seen = new Map(); // miningPda -> { solo, motherlode, status }
// One-time setup when a member gives you their username. Save the returned
// URL in your database or config; do not resolve the username at bot startup.
async function findUserApiUrl(username) {
const res = await fetch(`${BASE}/api/users/${encodeURIComponent(username)}/parties`);
if (!res.ok) throw new Error(`Unknown user: ${username}`);
const { userApiUrl } = await res.json();
return userApiUrl;
}
async function listMemberParties(memberId, userApiUrl) {
const res = await fetch(userApiUrl);
if (!res.ok) throw new Error(`Lookup failed for ${memberId}: HTTP ${res.status}`);
const { parties } = await res.json();
return parties;
}
async function checkParty(party) {
const res = await fetch(party.miningApiUrl);
if (!res.ok) throw new Error(`Party lookup failed: HTTP ${res.status}`);
const mining = await res.json();
const solo = mining.miningLog.lastSoloWin;
const ml = mining.miningLog.lastMotherlodeWin;
const before = seen.get(party.miningPda);
if (before) {
if (solo && solo.roundId > before.solo) {
notify(`${party.name} hit a SOLO: ${solo.oreWon} ORE in round ${solo.roundId}${shareLines(solo)}`);
}
if (ml && ml.roundId > before.motherlode) {
notify(`${party.name} won the Motherlode: ${ml.oreWon} ORE in round ${ml.roundId}${shareLines(ml)}`);
}
if (before.status === "mining" && mining.status === "complete") {
notify(`${party.name} finished mining with ${mining.assets.unrefinedOre} Unrefined ORE`);
}
}
seen.set(party.miningPda, {
solo: solo?.roundId ?? 0,
motherlode: ml?.roundId ?? 0,
status: mining.status,
});
}
// One line per holder: how much of a SOLO or Motherlode win their NFTs earned.
function shareLines(round) {
return (round.shares ?? [])
.map((share) => `\n ${share.username ?? share.wallet ?? "Unlinked wallet"}: ${share.oreWon} ORE (${share.nftsOwned} NFT)`)
.join("");
}
function notify(message) {
console.log(message); // send this to your Discord webhook instead
}
async function run() {
const parties = new Map(); // miningApiUrl -> Party; shared Parties appear once
for (const [memberId, userApiUrl] of members) {
try {
for (const party of await listMemberParties(memberId, userApiUrl)) {
if (party.miningApiUrl) parties.set(party.miningApiUrl, party);
}
} catch (error) {
console.error(error);
}
}
for (const party of parties.values()) {
await checkParty(party).catch(console.error);
}
}
run().catch(console.error);
setInterval(() => run().catch(console.error), 5 * 60 * 1000);Official notes from Orelana land in Messages.
