The score, by dimension
- the same for all 7
- #1 of 7 · best 17.8
- the same for all 7
- the same for all 7
- the same for all 7
Tick: the best in this ranking · Methodology v2026.11.1
TukTuk (Helium)
Solana crank protocol from Helium
#1 of all 7 worldwide80
- Rank
- #1 of all 7 worldwidere-runs: scores 80–81 and stays #1
- Your cost
- Not priced on this basis
- Evidence
- High4 of 4 criteria sourced
- Licence
- No MiCA record on file
- Freshness
- Read September 2026checked · re-read due
Check availability for your country
TukTuk (Helium) · tuktuk.fun. Provider links appear once we know which country you are browsing from: ChainChoice links to providers only where it serves in full.
Commission: This provider pays ChainChoice nothing for this link. Disclosure
Crypto products are high risk. Check the provider is authorised where you live before you deposit.
The verdict
TukTuk (Helium) is #1 of 7 published automation & keepers; it scores 8/10 on survives the vendor, where the category best is 9. Its widest gap is published lateness bound: 6/10, where DeFi Saver Automation scores 9. Choose DeFi Saver Automation if published lateness bound matters most.
Is TukTuk (Helium) right for you?
Suits you if
- Whether the job survives the vendor: who else can turn the crank, and what end-of-life is published8/10; the category best is 9
- What can fire the call, against what target, and who can check the condition was true8/10, the category best
- Whether a run that never happened is visible, or the job just goes quiet7/10, the category best
Look elsewhere if
- The lateness the vendor will put in writing, and the conditions under which it declines to execute6/10 here; DeFi Saver Automation scores 9
Not yet tested for your country. Markets it lists: Global.
to test where you can use it.
The rank above is the published one, the same for every reader. Find my best automation network shows where it lands for you.
What will TukTuk (Helium) cost you?
Not priced on this basis
- Usage per month
- 10
How safe is TukTuk (Helium)?
- Evidence: verified4 of 4 criteria rest on quoted, sourced receipts. Read September 2026.
- LicenceMiCA (EU): no register record on file here.
Entity: not verified. No hand-confirmed record on file ties TukTuk (Helium) to the company that runs it, so this page cannot say which other products that company operates. Read the legal entity in its terms before you deposit. How we read the evidence
Open the evidenceIf it doesn’t fit, choose
Compare all 4- 2KeeperHubIf published lateness bound matters most: 711 points below · stronger on published lateness bound (7 against 6)69
- 3Reactive Network12 points below · weaker on survives the vendor (2 against 8)68
- 4DeFi Saver AutomationIf published lateness bound matters most: 914 points below · stronger on published lateness bound (9 against 6)66
Provider at a glance
- Category
- Automation & Keepers
- Entity
- Not verified
- Official website
- tuktuk.fun
Independent rankingchecked How it works
Details
Scored 80 out of 100 under methodology 2026.11.1, from the evidence read in September 2026.
For your setup
Find out if TukTuk (Helium) fits you
The rank above is the published one — the same for every visitor. Answer the category's questions and this section shows where TukTuk (Helium) lands for you, which criteria your answers weight up, and which stated needs the record does or does not meet. The published rank stays beside it.
- A few questions
- No account required
- Ranking-blind: no commercial input
- Personalised in under 60 seconds
Find my best automation networkNothing is inferred from clicks, popularity or commercial value.
Why it leads
Why TukTuk (Helium) ranks #1
Each strength is read from evidence on a 0–10 ladder and weighted as the published methodology states. The 32 objective points these produce (23.7 here) sit inside the score; availability, friction, trust record and measured data add the rest. Best in this ranking on 2 of 4.
4 published criteria · Σ weight 100
CriterionWeightStrength · 0–10ScoreContrib.MedianBestRankEvidence
288+7.176.08#1/7
Primary
Provider page · read 2026-09-28308+7.684.09#2/7
Primary
Provider page · read 2026-09-28247+5.385.07#1/7
Primary
Provider page · read 2026-09-28186+3.466.09#4/7
Primary
Provider page · read 2026-09-28Hairline = best in this ranking · tick = its median · a missing bar is "not scored", never zero
Margin+11over KeeperHub, #2 of all 7 worldwide, on the published score
RobustnessHoldsacross a one-point change to each of its 4 criterion scores, the re-run scores 80–81 and stays #1
Evidence4 of 4 scored4 quoted, 4 with a source link
What would move the rank
Each line is the ranking run again with one of TukTuk (Helium)’s criterion scores changed and every other value held: the smallest whole-point change on that criterion that moves its rank, and where the re-run puts it. Up to 4 climbs and 3 falls are listed, smallest change first. Nothing here is a forecast.
Whether the job survives the vendor: who else can turn the crank, and what end-of-life is published 8 → 2 on its ladder · KeeperHub passes it−678#1 → #2
What can fire the call, against what target, and who can check the condition was true 8 → 1 on its ladder · KeeperHub passes it−777#1 → #2
Strengths
3 from the score dataWhere it leads
Best for readers who weight
- Whether the job survives the vendor: who else can turn the crank, and what end-of-life is published — 8/10, category best 9/10
- What can fire the call, against what target, and who can check the condition was true — 8/10, the category best
- Whether a run that never happened is visible, or the job just goes quiet — 7/10, the category best
Tradeoffs
1 from the score dataWhere it trails
Not for readers who put first
- The lateness the vendor will put in writing, and the conditions under which it declines to execute — 6/10 against a category best of 9/10
Record watch-outs
- Read this before committing: the programs are UPGRADEABLE and one authority controls both. tuktukUrfhXT6ZT77QTU8RQtvgL967uRuVagWF57zVA and cronAjRZnJn3MTP3B9kE62NWDrjSuAPVXf9c4hu4grM are owned by BPFLoaderUpgradeab1e11111111111111111111111, and their programData accounts both report the SAME upgrade authority, pULUgsYtKvT7qhsL8QJ2oJXYQUeCCdjtfawPnBqEr3U (read via getAccountInfo on mainnet-beta on 2026-08-14, and again at slot 451387271 on 2026-09-28). That account is system-owned with zero data; it held 2,426.04 SOL on 2026-08-14 and 200.00 SOL on 2026-09-28; whether it is a single keypair or a multisig vault cannot be determined from the account, and the vendor publishes nothing about who holds it. Everything this product scores well on — the unconstrained `crank_turner: Signer` that lets anyone execute your task — is code one key can replace (and that key did redeploy the tuktuk program at slot 448828254, matching release 0.2.11 on 2026-09-20), and there is no published continuity statement, sunset policy or security contact anywhere on the site or in its repository (no SECURITY.md, no CHANGELOG.md, /terms and /status both HTTP 404, status.tuktuk.fun NXDOMAIN). Three further things. (1) Firing is time-only: the published TriggerV0 enum is exactly {Now, Timestamp(i64)}, with cron expressions layered on by a second onchain program. There is no event, state, HTTP or cross-chain trigger. A conditional loop is supported without a server you own — a task's program can return its successor via RunTaskReturnV0, and the vendor publishes an instruction named `recurring_task` at https://www.tuktuk.fun/docs/api/cpi-example-sdk — but you must write and deploy that Solana program yourself; the platform evaluates nothing but the clock. (2) The executor count needs its caveat carried with it: seven distinct addresses ran RunTaskV0 in the August window, but four of them had their FIRST-EVER transaction funded from one wallet, 4SP9UEdkdPsFgEVmERLXZ4aUAFGCJ2JUuBgFyYAnv8AF, on 2026-08-11 — three in a single transaction. The chain supports 'at least two independent operator groups', not 'seven independent operators'. The set has since turned over: those four keys last ran on 2026-09-03, and a new address, BcS9rqkjquBDyi1faYqWYaLfW2Pc9fAXuBxoDHKYdYRM, first funded on 2026-09-02, paid for 47 of 50 runs sampled on 2026-09-28. No transfer read links its funder to 4SP9 or to the Helium-vanity keys, so its independence is unproven; the chain still shows at least two operator groups in the 30 days to 2026-09-28, but fewer are running today. (3) Nothing pushes: across all 23 published pages there is no webhook, alert, notification or email of any kind, so a defunded cron stops forever until a human polls — and the field the vendor's own monitoring page tells you to poll, removed_from_queue, is marked '// Deprecated: You should use the next_schedule_task instead' in the program source, while next_schedule_task appears on no page of the site. Separately, the homepage states the contracts are 'currently being audited. Use at your own risk.' with no auditor, report or date. PRICING, recorded as disclosure and ranked in no criterion: there is no subscription, no per-execution rate card and no vendor invoice. The buyer sets crank_reward per task in lamports (the CLI example at https://www.tuktuk.fun/docs/learn/create_a_task_queue uses --crank-reward 1000000, i.e. 0.001 SOL) and whichever anonymous signer executes it collects it; a live successful run logged 'Program log: Paying out reward 15000' (15,000 lamports) in signature 3iRR1cX8S7gbe3KiLDkG3KMhFu4V5D156YsaRPvibA9nnqhc7D6afoHxJpTraQsouKmhT3ewppsxfTR5fKXZSoLQ, slot 439184245, read on mainnet-beta 2026-08-14. That the crank reward is the ONLY fee is now verified rather than assumed: across all 17 .rs files of the tuktuk program, `uncollected_protocol_fees` appears exactly three times — twice as a struct field declaration in state.rs and once initialised to 0 in initialize_task_queue_v0.rs — with no code path anywhere that increments it. Pricing-shaped URLs tried, all HTTP 404 on 2026-08-14: /pricing, /docs/pricing, /terms.
Competitive position
How TukTuk (Helium) places on each criterion
Rank on every objective dimension among the rows scored on it. A criterion in the top third of its pool is listed as a lead, the bottom third as a trail; the middle is neither. Popularity, size and commercial terms are not dimensions.
Against #2
80 vs 69 · gap 11.0Why TukTuk (Helium) ranks above KeeperHub
DimensionThisKeeperHubGap share
Availability · 23% weight · constant here14.014.0same
Published criteria · 35% weight17.813.7+10.7, better
Friction · 12% weight · constant here2.72.7same
Trust record · 9% weight · constant here3.23.2same
Measured data · 21% weight · constant here8.38.3same
Published criterionThisKeeperHubPoints
What can fire the call, against what target, and who can check the condition was true · w2886+1.79, better
Whether the job survives the vendor: who else can turn the crank, and what end-of-life is published · w3086+1.92, better
Whether a run that never happened is visible, or the job just goes quiet · w2474+2.30, better
The lateness the vendor will put in writing, and the conditions under which it declines to execute · w1867−0.58, worse
Net8069+11.0
Your scenario
TukTuk (Helium) is not priced for this scenario
Metered usage beyond whatever the plan includes, for a year. Excludes egress, support tiers and enterprise minimums. Change an input and every figure recomputes from the published rate; the published rank does not move.
your cost/yr · default scenario — set your own
Usage per month · your input10
Rate read from the provider’s published pricing ↗ on 28 September 2026.
your cost/yrCost is stated as your cost/yr in USD; it is never a yield, never annualised, and it does not enter the score.
Not priced on this basis
Under the default inputs · USDTypical costNot statedFewer than 5 priced rows: no typical cost is named · 0 of 7 rows priced
Lowest fee, priced rowsNone pricedDifference not stated · availability not applied — set your country to filter
7 of 7 rows in this ranking have no verified rate for this scenario and are absent from the typical, not counted as free.
Evidence
Evidence read 28 September 2026
One row per published criterion: the page each strength was read from, its source type by domain, the reading date and whether the file and the published table agree. Open a row for the quote and the receipt.
4 of 4 cells scored
Score evidenceVerified4 of 4 criteria reconstruct from receipts
4 of 4 criteria reconstruct from a quoted, sourced receipt equal to the published strength.Public receiptsReading…4 quoted with a source URL
The receipt file has not been read yet.Evidence confidenceHighcoverage and corroboration, never freshness
4/4 criteria scored, with 4 dated sources quoted.RobustnessHoldsrank #1 across every one-point re-run
Whether the position holds when one criterion score is changed by one point and the ranking is run again. It is always a re-run of the ranking, never an estimate.The newest evidence read on the platform is 10 November 2026; this category's reading is older. The scores stand as read on 28 September 2026.
CriterionSourceTypeReadFreshnessStatusReceipt
What can fire the call, against what target, and who can check the condition was truestrength 8 · weight 28Report an errorProvider's own page28 September 2026…
Verified
The published strength matches the evidence cell and a source page is on file.Whether the job survives the vendor: who else can turn the crank, and what end-of-life is publishedstrength 8 · weight 30Report an errorProvider's own page28 September 2026…
Verified
The published strength matches the evidence cell and a source page is on file.Whether a run that never happened is visible, or the job just goes quietstrength 7 · weight 24Report an errorProvider's own page28 September 2026…
Verified
The published strength matches the evidence cell and a source page is on file.The lateness the vendor will put in writing, and the conditions under which it declines to executestrength 6 · weight 18Report an errorProvider's own page28 September 2026…
Verified
The published strength matches the evidence cell and a source page is on file.How you can lose money here, and what the ranking scores
- Control failure (TukTuk (Helium) 8/10): a key or vote changes the rules, freezes or mints.Scored by What can fire the call, against what target, and who can check the condition was true · 28%
- Liveness failure (TukTuk (Helium) 7/10): the operator stops, censors you or loses data.Scored by Whether a run that never happened is visible, or the job just goes quiet · 24%
- Execution failure (TukTuk (Helium) 6/10): you get a worse price, later, or nothing.Scored by The lateness the vendor will put in writing, and the conditions under which it declines to execute · 18%
- Exit failure (TukTuk (Helium) 8/10): you cannot get out at par, on time, or with what is yours.Scored by Whether the job survives the vendor: who else can turn the crank, and what end-of-life is published · 30%
Every failure family that applies to this category is scored.
Facts
facts, not scoresWhat the record publishes
- Pricing
- No rate card, subscription or vendor invoice exists; the only price mechanics are on https://
www .tuktuk .fun /docs /overview, fetched 28 September 2026 and unchanged since August: "Creators of Task Queues set their payment per-crank turn in SOL. Crankers that run the tasks are paid out in SOL for each crank they complete. There is a minimum deposit of 1 SOL to create a task queue to discourage spam. This deposit is refunded when the task queue is closed." The buyer sets the reward per task and whichever signer executes the task collects it. Chain read, not a page price: a RunTaskV0 on Solana mainnet-beta on 28 September 2026 (signature 2fLreLZZjjAgHpVC9ZPURc12y8ZC5mZvJBCBWgxULQPTMpHEJ2u3dhkGScEn2CCAbYSR4i9pELtSiKhS55j7qEEY, slot 451277684) logged "Paying out reward 15000", i.e. 15,000 lamports (0.000015 SOL) to the executor. https:// www .tuktuk .fun /pricing returns HTTP 404.TukTuk (Helium) — official pricing page ↗ · 28 September 2026 - Prices published in
- USDTukTuk (Helium) — official pricing page ↗ · 28 September 2026
- Licences held
- Not published
- Compliance level
- partial
- Regulatory note
- Not published
- Supported chains
- solana
- Markets served
- global
- Primary markets
- Not published
- Restricted markets
- Not published
- Operating limits
- Not published
- Availability note
- Global, and unrestricted in the strict sense — re-verified 14 August 2026 against the vendor's own availability prose, of which there is none. TukTuk is an onchain Solana program plus Apache-2.0 crates; there is no account, no signup, no KYC and no vendor-side gate between the buyer and execution. Buyers interact by sending a QueueTaskV0 instruction from any Solana keypair, and executors run `cargo install tuktuk-crank-turner` from crates.io. A full-corpus text search across all 23 live tuktuk.fun pages returns ZERO occurrences of 'jurisdiction', 'restricted', 'prohibited', 'KYC', 'sanction', 'terms of service', 'privacy policy' or 'acceptable use'. No such document exists to restrict anyone: https://
www .tuktuk .fun /terms and https:// www .tuktuk .fun /privacy both return HTTP 404, and neither is linked from the homepage or /docs. The repository tree (359 entries) carries only LICENSE (Apache-2.0) and README.md — no SECURITY.md, no CONTRIBUTING.md, no terms. The one caution the vendor does publish is not geographic: 'Smart contracts currently being audited. Use at your own risk.' (https:// www .tuktuk .fun /). Chain scope, not geography, is the real limit: Solana only. Mainnet-beta is verified onchain above; a devnet feature flag exists in the program manifests (https:// github .com /helium /tuktuk /blob /main /solana-programs /programs /cron /Cargo .toml) but no non-Solana deployment is claimed or found anywhere.
No confirmed legal entity is on file for this record. Nothing is inferred from the brand name.
If something goes wrong with TukTuk (Helium): where to complain, and where to report a scam
Loading the routes for your country.
How this page is reviewed
Reviewed means this product in this category was read against its sources on or after that date; every ranked category is re-read at least every 45 days. Models research, extract and parse. A deterministic engine ranks. Every quote passes an adversarial refute pass.
Accountable for this review: Mathias Siemonsmeier, Founder.
How we review · Review calendar · Corrections log · How we make money
History
What the record carries
Changes to published ranks are recorded in a ledger; every step and its cause is listed on the rank-history page. The entries below begin with the current verified snapshot, then the methodology versions whose changes applied to this category, newest first.
9 methodology entries
- 28 September 2026Current verified snapshot · methodology 2026.11.1Score 80, #1 of 7. 4 of 4 criteria scored. History starts here; earlier values are not interpolated.
- 10 October 2026
2026.10.8When nothing serves your country, the list shown for reference is the published ranking · platform-wide- fixed The reference list shown when nothing serves your country is the published order with the published scores, and a build check now fails any such list out of that order or with a score the ranking does not publish.
- fixed The explorer prints an overall rank only for a row the published ranking holds; a country entrant such as Coinbase Commerce for US merchants shows no overall rank.
- changed Published orders do not move. Country results change only where nothing serves the country: in India bill pay keeps Bitcoin Well first and now shows Strike second, as published; 35 such runs across all categories and countries now match the published list exactly.
- 10 October 2026
2026.10.6A criterion you require re-scores the rows that meet it · platform-wide- changed The explorer sends each criterion you require, at any band, as fit_required with your other answers; region, licence, chain and fact filters stay filters. On /best, a required criterion joins For you as a marked preference does, which needs your country; Overall stays the published ranking, filtered.
- added Every published criterion has a golden case as the explorer sends it (require:<criterion>), so the order a requirement gives is replayed and gated as the published order is, and a change to it needs an entry here.
- 16 September 2026
2026.09.15Dimension scores carry tenths, and eleven more categories are re-read from primary sources · platform-wide- changed Dimension scores resolve to tenths of a point (O-04b), and weightedTotal is rounded to six decimal places before the order is read. 518 published scores move across 107 categories that were not re-read; none of them moves by more than 4 points, and most move by 1.
- fixed 66 published scores change in the eleven re-read categories, against a verbatim source each. The largest moves are Reflexer RAI (−16), Beefy and Unrekt (−11), Aztec (−10) and Golem (+9) — all of them rows whose sources had moved since their last read.
- changed Published order moves in 38 of 119 categories and three #1s change: smart_contract_audits (Zellic → Certora) and travel_rule_compliance (Sumsub Travel Rule → CodeVASP) on the finer resolution, kyc_compliance (Veriff → Sumsub) on the re-read.
- added availabilitySource (O-04g): for a reader who states a country, a row whose availability in that country rests on a region tag its record gives no source for sorts below every sourced row. It is inert in every order published here, which states no country.
Methodology 2026.11.1, the same published run every visitor sees · receipt automation_keepers:tuktuk:2026.11.1:89ccfa60e9be
Are you TukTuk (Helium)? Reply to this verdict, or send evidence, ask for a correction or claim the listing. Every message gets a public ticket number; none of it changes a rank unless a public page or a signed statement supports it.