hosting contract not deployed on devnet — missing from deploy_services.rhai provision script #44

New issue

Open

opened 2026-04-11 01:28:51 +00:00 by mik-tf · 0 comments

mik-tf commented

2026-04-11 01:28:51 +00:00

Owner

Problem

The hosting contract (source at contracts/hosting/) is not deployed on the devnet chain. It is not part of scripts/rhai/provision/deploy_services.rhai — only 11_deploy_hosting.rhai exists under examples/rhai/contracts/deploy/, which is not run as part of standard provisioning.

Verified on 2026-04-10 via authenticated account.exists queries against https://ledger.dev.projectmycelium.com/rpc:

Account	Exists
`dev.hero` (root)	✅
`faucet.dev.hero`	✅
`identity.dev.hero`	✅
`dns.dev.hero`	✅
`marketplace.dev.hero`	✅
`spore.dev.hero`, `gld.dev.hero`, `usdh.dev.hero`	✅
`hosting.dev.hero`	❌ does not exist

(Also checked alt names: hosting.hero, grid.dev.hero, tfgrid.dev.hero, farm.dev.hero, farms.dev.hero, compute.dev.hero, nodes.dev.hero, hosting.marketplace.dev.hero, hosting.mycelium, hosting — all absent.)

Confirmed via rpc.discover on the devnet gateway too: 43 total methods, zero hosting.* methods exposed.

Context

This came up while working on Phase 3 of the marketplace scaling architecture initiative (mycelium_code/home#72) — hero_compute_server first-boot hook is supposed to call hosting.farm_create + hosting.node_register via direct near-jsonrpc-client. Those calls will fail with AccountDoesNotExist until the contract is live on devnet.

Not blocking our Phase 3 code work — we plan to implement and test Phase 3 using near-workspaces-rs sandbox tests that compile and deploy the hosting contract WASM in-process, which is how NEAR contracts are idiomatically tested anyway. But we do need the devnet deployment before the final E2E validation step.

Proposed fix

PR opened: #45 — 13-line diff adding a hosting deploy block to deploy_services.rhai, modeled on the existing DNS and Marketplace blocks. Hosting contract compiles cleanly on wasm32-unknown-unknown from current source, no new dependencies.

Alternative if preferred: run the existing examples/rhai/contracts/deploy/11_deploy_hosting.rhai script directly against devnet as a one-shot. Faster but leaves the provision script out of sync.

Ask

@scott — whenever convenient, either merge PR #45 and re-run provision against devnet, or run 11_deploy_hosting.rhai directly. Non-urgent — we can continue Phase 3 code and tests without it.

PR: #45
Scaling architecture initiative: mycelium_code/home#72 (Phase 3)
Spec doc §Phase 3.0 HARD CHECKPOINT — we now know the checkpoint was incomplete: it verified implicit accounts work but did not verify the hosting contract itself is deployed

## Problem The `hosting` contract (source at `contracts/hosting/`) is not deployed on the devnet chain. It is not part of `scripts/rhai/provision/deploy_services.rhai` — only `11_deploy_hosting.rhai` exists under `examples/rhai/contracts/deploy/`, which is not run as part of standard provisioning. Verified on 2026-04-10 via authenticated `account.exists` queries against `https://ledger.dev.projectmycelium.com/rpc`: | Account | Exists | |---|---| | `dev.hero` (root) | ✅ | | `faucet.dev.hero` | ✅ | | `identity.dev.hero` | ✅ | | `dns.dev.hero` | ✅ | | `marketplace.dev.hero` | ✅ | | `spore.dev.hero`, `gld.dev.hero`, `usdh.dev.hero` | ✅ | | **`hosting.dev.hero`** | **❌ does not exist** | (Also checked alt names: `hosting.hero`, `grid.dev.hero`, `tfgrid.dev.hero`, `farm.dev.hero`, `farms.dev.hero`, `compute.dev.hero`, `nodes.dev.hero`, `hosting.marketplace.dev.hero`, `hosting.mycelium`, `hosting` — all absent.) Confirmed via `rpc.discover` on the devnet gateway too: 43 total methods, zero `hosting.*` methods exposed. ## Context This came up while working on Phase 3 of the marketplace scaling architecture initiative ([mycelium_code/home#72](https://forge.ourworld.tf/mycelium_code/home/issues/72)) — `hero_compute_server` first-boot hook is supposed to call `hosting.farm_create` + `hosting.node_register` via direct `near-jsonrpc-client`. Those calls will fail with `AccountDoesNotExist` until the contract is live on devnet. **Not blocking our Phase 3 code work** — we plan to implement and test Phase 3 using `near-workspaces-rs` sandbox tests that compile and deploy the hosting contract WASM in-process, which is how NEAR contracts are idiomatically tested anyway. But we do need the devnet deployment before the final E2E validation step. ## Proposed fix PR opened: https://forge.ourworld.tf/lhumina_code/hero_ledger/pulls/45 — 13-line diff adding a hosting deploy block to `deploy_services.rhai`, modeled on the existing DNS and Marketplace blocks. Hosting contract compiles cleanly on `wasm32-unknown-unknown` from current source, no new dependencies. Alternative if preferred: run the existing `examples/rhai/contracts/deploy/11_deploy_hosting.rhai` script directly against devnet as a one-shot. Faster but leaves the provision script out of sync. ## Ask @scott — whenever convenient, either merge PR #45 and re-run provision against devnet, or run `11_deploy_hosting.rhai` directly. Non-urgent — we can continue Phase 3 code and tests without it. ## Related - PR: https://forge.ourworld.tf/lhumina_code/hero_ledger/pulls/45 - Scaling architecture initiative: https://forge.ourworld.tf/mycelium_code/home/issues/72 (Phase 3) - Spec doc §Phase 3.0 HARD CHECKPOINT — we now know the checkpoint was incomplete: it verified implicit accounts work but did not verify the hosting contract itself is deployed