
{"id":228331,"date":"2026-09-16T15:34:29","date_gmt":"2026-09-16T15:34:29","guid":{"rendered":"https:\/\/mycryptomania.com\/?p=228331"},"modified":"2026-09-16T15:34:29","modified_gmt":"2026-09-16T15:34:29","slug":"minara-fun-api-on-arc-track-launches-trades-and-volume","status":"publish","type":"post","link":"https:\/\/mycryptomania.com\/?p=228331","title":{"rendered":"Minara.fun API on Arc: track launches, trades and volume"},"content":{"rendered":"<p>Minara.fun produced 1,417 token launches in its first 6 hours and 2 minutes on Arc mainnet. By 14:40 UTC on September 16, 2026, 1,312 of those tokens had traded. Their Minara pools recorded 168,208 swaps and $22.59 million in gross USDC volume after exact duplicate data rows were\u00a0removed.<\/p>\n<p>Disclosure: This story was prepared for Bitquery and uses its API. I used AI assistance to organize, draft, and edit the story; I checked the queries, contracts, and figures against the cited\u00a0data.<\/p>\n<p>In this guide, \u201cMinara.fun API\u201d means Bitquery\u2019s GraphQL access to Minara\u2019s public on-chain data. Minara supplies the contracts and activity; Bitquery supplies the query service used\u00a0below.<\/p>\n<h4>What Minara.fun launched on\u00a0Arc<\/h4>\n<p><a href=\"https:\/\/minara.fun\/\">Minara.fun<\/a> is a token launchpad built for <a href=\"https:\/\/www.arc.io\/blog\/arc-mainnet-goes-live-on-september-16-2026\">Circle\u2019s Arc mainnet<\/a>. A launch creates a token and opens a Uniswap v4 pool in one transaction. Arc\u2019s native asset is USDC, so users pay gas in USDC and Minara\u2019s main pools use USDC as the quote\u00a0asset.<\/p>\n<p>That setup makes the data easier to read. The amount moving through the quote side is already in a dollar asset. It also gives an analytics app a clear chain of records: the launch event names the token and pool, while the pool\u2019s later swap rows carry the price, wallet, direction, and USDC\u00a0amount.<\/p>\n<p>Minara\u2019s <a href=\"https:\/\/api.minara.fun\/minara-fun\/contracts?chainId=5042\">mainnet contract registry<\/a> listed these addresses during the\u00a0check:<\/p>\n<p>Launch strategy: 0x4D3a3f4e1a918845C2038Bc064C4d250822B203eToken factory: 0xFf99D8f6C994607576eB652EDCf12E04a7EbfBf6Fee hook: 0xb6A65950534F061618B4AE102FBcbb8541a8e0cCUniswap v4 PoolManager: 0x8366a39CC670B4001A1121B8F6A443A643e40951<\/p>\n<p>Read that registry when your app starts. Minara\u2019s current strategy address can\u00a0change.<\/p>\n<h4>Six hours of Minara.fun activity<\/h4>\n<p>The study starts at the first successful TokenLaunched event, 08:37:48 UTC, and stops at 14:40:00 UTC on September 16. Arc public mainnet had not existed for a full day, so a \u201clast 24 hours\u201d figure would have been false precision.<\/p>\n<p>About 92.6% of the launched tokens had traded by the cutoff. The pace peaked between 09:30 and 10:00 UTC, when 319 launches landed in 30 minutes. Across the full window, the mean was close to four launches per\u00a0minute.<\/p>\n<p><em>Minara.fun launches by 30-minute interval. The first and final bars are partial intervals. Source: Bitquery; 08:37:48\u201314:40:00 UTC, September 16,\u00a02026.<\/em><\/p>\n<p>Trading was concentrated. A token named Minara, at 0xa163\u202661bb, accounted for $9.63 million, or 42.6% of the measured volume. The four busiest Minara pools made up 70.9% of all volume in the\u00a0window.<\/p>\n<p><em>Gross USDC volume in the five busiest Minara pools. Token names are on-chain labels, not verified identities. Source: Bitquery; same fixed\u00a0window.<\/em><\/p>\n<p>These numbers describe turnover, not revenue, liquidity, or money raised. Anyone can create a token with an arbitrary name. A label such as \u201cMinara\u201d does not prove that the token came from, or is backed by, the Minara\u00a0team.<\/p>\n<h4>Prove the launch before counting\u00a0it<\/h4>\n<p>Minara\u2019s TokenLaunched event has this signature hash:<\/p>\n<p>3b3d2bafdcae274a232217e1f80ee4305d3af6aa25c8b14b1681bd68d18042a4<\/p>\n<p>The first indexed topic after the event hash contains the Uniswap v4 pool ID. The next topic contains the token address, padded to 32 bytes. Keep the transaction hash and log index as the row\u00a0ID.<\/p>\n<p>A stronger check reads four events from the same transaction. The token factory emits TokenCreated; the PoolManager emits Initialize; the approved strategy emits TokenLaunched; and the Minara fee hook emits PoolRegistered. The token and pool ID must agree across those\u00a0records.<\/p>\n<p>My first pass filtered on the launched token addresses. It returned $26.72 million. The query was also catching secondary pools that Minara did not create. After I switched to the pool IDs emitted by the launch transactions and removed exact duplicate rows, the measured total fell to $22.59\u00a0million.<\/p>\n<p>For example, the launch of 0xa163\u202661bb appeared in transaction 0xf4bda4\u2026747b. Its factory event was followed by pool initialization, hook registration, and the strategy\u2019s launch event. The agreed pool ID was 0xd77a\u2026b150. That pool, rather than every market carrying the same token address, became the filter for the trade and candle\u00a0queries.<\/p>\n<p>This separation matters on launch day. A popular token can gain extra pools within minutes. A token-wide volume query then answers a different question: how much the token traded across Arc. A pool-ID query answers how much moved through the market created by Minara.fun.<\/p>\n<h4>Query recent Minara.fun launches<\/h4>\n<p>Paste the query into the <a href=\"https:\/\/ide.bitquery.io\/\">Bitquery IDE<\/a>. It reads Arc mainnet only and returns the newest successful launch records from the current strategy.<\/p>\n<p>query RecentMinaraLaunches {<br \/>  EVM(network: arc) {<br \/>    Events(<br \/>      limit: {count: 20}<br \/>      orderBy: {descending: Block_Time}<br \/>      where: {<br \/>        TransactionStatus: {Success: true}<br \/>        LogHeader: {<br \/>          Address: {is: &#8220;0x4d3a3f4e1a918845c2038bc064c4d250822b203e&#8221;}<br \/>          Removed: false<br \/>        }<br \/>        Log: {Signature: {SignatureHash: {is: &#8220;3b3d2bafdcae274a232217e1f80ee4305d3af6aa25c8b14b1681bd68d18042a4&#8221;}}}<br \/>      }<br \/>    ) {<br \/>      Block {Number Time}<br \/>      Transaction {Hash From}<br \/>      LogHeader {Index}<br \/>      Topics {Hash}<br \/>    }<br \/>  }<br \/>}<\/p>\n<p>For each result, take the pool ID and token address from the indexed topics. Before saving the row, run the four-event check\u00a0above.<\/p>\n<h4>Read recent trades from one Minara\u00a0pool<\/h4>\n<p>Uniswap v4 uses one PoolManager contract for many pools. Its contract address is not a pool filter. Use Pair.Pool.Id, taken from the verified launch\u00a0event.<\/p>\n<p>query RecentTradesForMinaraPool {<br \/>  Trading {<br \/>    Trades(<br \/>      limit: {count: 20}<br \/>      orderBy: {descending: Block_Time}<br \/>      where: {<br \/>        Pair: {<br \/>          Market: {Network: {is: &#8220;Arc&#8221;}}<br \/>          Pool: {Id: {is: &#8220;0xd77a1efbc8d143b100cf2496ff970da0a616a6796886e6ba1f45e7d7e09bb150&#8221;}}<br \/>        }<br \/>      }<br \/>    ) {<br \/>      Block {Time}<br \/>      TransactionHeader {Hash Index}<br \/>      Trader {Address}<br \/>      Side<br \/>      Amounts {Base Quote}<br \/>      AmountsInUsd {Quote}<br \/>      PriceInUsd<br \/>      Pair {<br \/>        Token {Id Address Symbol}<br \/>        QuoteToken {Id Address Symbol}<br \/>        Pool {Id Address}<br \/>        Market {Network Protocol}<br \/>      }<br \/>    }<br \/>  }<br \/>}<\/p>\n<p>Use AmountsInUsd.Quote for dollar volume. The quote side is the sound measure for these USDC pools; the base-side USD field uses a reference price that can drift during quick\u00a0moves.<\/p>\n<h4>Rank Minara tokens by USDC\u00a0volume<\/h4>\n<p>Build the pool-ID list from verified launch events, then pass it to Trading.Trades. The sample uses the five busiest pools so it stays readable. A production job can submit the full list in batches and merge rows by pool\u00a0ID.<\/p>\n<p>query TopMinaraTokensByVolume {<br \/>  Trading {<br \/>    Trades(<br \/>      limit: {count: 10}<br \/>      orderBy: {descendingByField: &#8220;volume_usd&#8221;}<br \/>      where: {<br \/>        Pair: {<br \/>          Market: {Network: {is: &#8220;Arc&#8221;} Protocol: {is: &#8220;uniswap_v4&#8221;}}<br \/>          Pool: {Id: {in: [<br \/>            &#8220;0xd77a1efbc8d143b100cf2496ff970da0a616a6796886e6ba1f45e7d7e09bb150&#8221;<br \/>            &#8220;0xd67fdb79ceb19fe7c671b3def4fec48bef2322ec45e8e3b72ca918b77f1d218e&#8221;<br \/>            &#8220;0x1857b4a03254e13d44f1fd50010c4eb2e6de774681d960f83d1ccd728e802602&#8221;<br \/>            &#8220;0x1a81b70aef20a111df2dda2be549fef7736b7ec2196856c0d6704bb0135cad47&#8221;<br \/>            &#8220;0x8923c2bd0d514997173fc0a6813ee2b7875daa9d89b76e9e98c76a3ed13b3e09&#8221;<br \/>          ]}}<br \/>        }<br \/>        Block: {Time: {since: &#8220;2026-09-16T08:37:48Z&#8221; till: &#8220;2026-09-16T14:40:00Z&#8221;}}<br \/>      }<br \/>    ) {<br \/>      Pair {Token {Id Address Symbol Name} Pool {Id}}<br \/>      swaps: count<br \/>      traders: count(distinct: Trader_Address)<br \/>      volume_usd: sum(of: AmountsInUsd_Quote)<br \/>    }<br \/>  }<br \/>}<\/p>\n<p>The Trading cube contained 163 exact duplicate rows in the full Minara set, a rate of 0.097%. For audited totals, I removed duplicates using pool ID, transaction hash, trader address, side, and base amount. Keep that check in any report that presents an exact trade count or volume\u00a0total.<\/p>\n<p>The raw query returned 168,371 rows. After the duplicate check, 168,208 remained. Distinct transaction hashes totaled 167,337, slightly below the swap count because one transaction can contain more than one swap. This is why a transaction count should not be presented as a swap\u00a0count.<\/p>\n<h4>Build five-minute OHLCV\u00a0candles<\/h4>\n<p>Use Trading.Pairs when you need candles for one verified v4 pool. A duration of 300 means five\u00a0minutes.<\/p>\n<p>query MinaraPoolFiveMinuteCandles {<br \/>  Trading {<br \/>    Pairs(<br \/>      limit: {count: 100}<br \/>      orderBy: {ascending: Block_Time}<br \/>      where: {<br \/>        Market: {Network: {is: &#8220;Arc&#8221;}}<br \/>        Token: {Id: {is: &#8220;bid:arc:0xa163d7624da3b5d9182c50eab5b8cd247ae861bb&#8221;}}<br \/>        Pool: {Id: {is: &#8220;0xd77a1efbc8d143b100cf2496ff970da0a616a6796886e6ba1f45e7d7e09bb150&#8221;}}<br \/>        Interval: {Time: {Duration: {eq: 300}}}<br \/>        Block: {Time: {since: &#8220;2026-09-16T08:37:48Z&#8221; till: &#8220;2026-09-16T14:40:00Z&#8221;}}<br \/>      }<br \/>    ) {<br \/>      Token {Id Address Symbol}<br \/>      QuoteToken {Id Address Symbol}<br \/>      Pool {Id Address}<br \/>      Interval {Time {Start End Duration}}<br \/>      Price {Ohlc {Open High Low Close}}<br \/>      Volume {Base Usd}<br \/>    }<br \/>  }<br \/>}<\/p>\n<p>This query returned 71 five-minute candles for the leading pool in the fixed window. Empty intervals are normal when no swap\u00a0occurs.<\/p>\n<h4>What to build with the\u00a0data<\/h4>\n<p>A launch feed can start with EVM.Events, verify the transaction, then watch the matching pool through Trading.Trades. Store the block time, transaction hash, log index, token address, pool ID, and strategy address. That record gives every later query a clean starting\u00a0point.<\/p>\n<p>From there, you can add alerts for new launches, a pool-level trade tape, price charts, or wallet activity. If the app must react at once, turn the launch and trade queries into subscriptions and connect through Bitquery\u2019s GraphQL WebSocket endpoint. Keep the API token on your\u00a0server.<\/p>\n<p>Plan for brief WebSocket drops. Save the last processed block and log index, then request a small overlap before reconnecting. Remove rows already held by your app. The overlap is safer than assuming the first message after a reconnect follows the final message seen before\u00a0it.<\/p>\n<p>Refresh Minara\u2019s registry on a schedule as well. Event signatures can remain stable while an approved strategy address changes. Saving the strategy address beside each launch makes an old record reproducible without forcing today\u2019s address onto yesterday\u2019s data.<\/p>\n<p>I covered the wider chain setup in my earlier guide to the <a href=\"https:\/\/medium.com\/coinmonks\/arc-blockchain-api-query-circles-chain-with-bitquery-acbecbd06dc2\">Arc blockchain API with Bitquery<\/a>. For the current data fields and more examples, use Bitquery\u2019s <a href=\"https:\/\/docs.bitquery.io\/docs\/blockchain\/arc-mainnet\/arc-mainnet-launchpads-api\/\">Arc launchpad API documentation<\/a>.<\/p>\n<p><a href=\"https:\/\/medium.com\/coinmonks\/minara-fun-api-on-arc-track-launches-trades-and-volume-07a2effd111a\">Minara.fun API on Arc: track launches, trades and volume<\/a> was originally published in <a href=\"https:\/\/medium.com\/coinmonks\">Coinmonks<\/a> on Medium, where people are continuing the conversation by highlighting and responding to this story.<\/p>","protected":false},"excerpt":{"rendered":"<p>Minara.fun produced 1,417 token launches in its first 6 hours and 2 minutes on Arc mainnet. By 14:40 UTC on September 16, 2026, 1,312 of those tokens had traded. Their Minara pools recorded 168,208 swaps and $22.59 million in gross USDC volume after exact duplicate data rows were\u00a0removed. Disclosure: This story was prepared for Bitquery [&hellip;]<\/p>\n","protected":false},"author":0,"featured_media":228332,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-228331","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-interesting"],"_links":{"self":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/posts\/228331"}],"collection":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=228331"}],"version-history":[{"count":0,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/posts\/228331\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/media\/228332"}],"wp:attachment":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=228331"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=228331"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=228331"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}