# Ura Finance — Ecosystem Contributions

- Canonical page: https://partners.ura.finance/contributions
- Machine-readable mirror: https://partners.ura.finance/contributions.md
- Last updated: 2026-07-23

Open technical research, reproducible evidence and infrastructure proposals supporting Midnight, Lace, Mithril and privacy-first application development.

## Evidence discipline

Ura separates proven behavior, staged implementation and external blockers. Failed or ambiguous experiments are retained as evidence rather than presented as successful deployments.

## Status definitions

- **MERGED:** Accepted into an upstream public repository or standard track.
- **PROVEN:** Reproduced with retained public or sanitized evidence; does not claim an external root-cause conclusion unless stated.
- **PROPOSED:** Public proposal or staged implementation; not an adopted standard or production claim.
- **WAITING ON EXTERNAL TEAM:** Ura work is published or packaged; progress depends on an external maintainer or protocol team.

Statuses and claims should be interpreted according to the evidence discipline above. No external endorsement is claimed.

## Standards and protocol work

### MIP-0008 — CAIP-2 network identifiers for Midnight

Status: **MERGED**

Ura drafted and submitted the Midnight Improvement Proposal that defines CAIP-2 network identifiers in the midnight:{reference} form, supporting wallet and interoperability tooling downstream of MPS-0003.

Why it matters: Shared network identifiers reduce ambiguity across wallets, dApps and bridge tooling when addressing Midnight mainnet and test networks.

Links:
- [Merged MIP PR #186](https://github.com/midnightntwrk/midnight-improvement-proposals/pull/186)
- [Public MIP source](https://github.com/midnightntwrk/midnight-improvement-proposals/blob/main/mips/mip-0008-caip-2-network-identifiers.md)
- [Related OWS #222](https://github.com/open-wallet-standard/core/issues/222)

### Ura Capacity Protocol / Relay Club

Status: **PROPOSED**

Active proposal and staged build for privacy-preserving capacity routing — not an adopted Midnight standard.

- Model A: future-DUST generation routing from selected NIGHT/tNIGHT sources.
- Model B: sponsored application execution (application sponsorship).
- Pool-level conservation, receipts and independently checkable accounting.

Links:
- [Capacity Exchange overview (gist)](https://gist.github.com/alba-press/ce526cfce098a9970f1ef12daee437db)
- [Related Service Desk #106](https://github.com/midnightntwrk/servicedesk/issues/106)

## Lace connector contributions

### Lace #2242 — Future-DUST redesignation connector

Status: **WAITING ON EXTERNAL TEAM**

Connector feature request with a published draft dApp/wallet interface proposal covering capability discovery, wallet-managed source selection, preview, explicit confirmation, execution and status reporting.

Internal reference: LW-15175 · Status: waiting on Lace

Links:
- [Public issue #2242](https://github.com/input-output-hk/lace/issues/2242)
- [Interface proposal v0.1 comment](https://github.com/input-output-hk/lace/issues/2242#issuecomment-5053981493)
- [Related Service Desk #77](https://github.com/midnightntwrk/servicedesk/issues/77)

### Lace #2243 — Preprod wallet readiness

Status: **PROVEN**

Controlled cross-network comparison of the same Lace readiness timing methodology. The issue remains assigned to Lace and under investigation. Ura does not claim an internal root cause.

- **Preprod:** 3/3 connected, then all seven wallet-backed calls failed through 10 seconds with InternalError / Wallet is unavailable.
- **Preview:** 3/3 immediate wallet-backed success.
- **Mainnet:** 3/3 immediate wallet-backed success.

Internal reference: LW-15158 · Sanitized evidence package attached on the public evidence comment.

Links:
- [Public issue #2243](https://github.com/input-output-hk/lace/issues/2243)
- [Published evidence comment](https://github.com/input-output-hk/lace/issues/2243#issuecomment-5055461940)
- [Related Service Desk #80](https://github.com/midnightntwrk/servicedesk/issues/80)

## Midnight engineering support

### Service Desk #105 — Duplicate runtime identity

Status: **PROVEN**

Investigation of duplicate runtime identity and establishment of a supported singleton layout. The technical issue was resolved and the public ticket was closed.

Links:
- [Service Desk #105](https://github.com/midnightntwrk/servicedesk/issues/105)

### Service Desk #106 — DustRegistration / sponsorship routes

Status: **WAITING ON EXTERNAL TEAM**

Ura supplied the requested documentation-gap / observability-gap / bug classification and a controlled Preprod validation scenario. Waiting for the protocol team to identify the authoritative semantics and supported surfaces. No workaround is claimed.

Links:
- [Service Desk #106](https://github.com/midnightntwrk/servicedesk/issues/106)
- [Public classification and validation scenario](https://github.com/midnightntwrk/servicedesk/issues/106#issuecomment-5060953166)

### Service Desk #109 — Runtime-package licensing

Status: **WAITING ON EXTERNAL TEAM**

The missing runtime-license metadata question was split from #105 at a Midnight engineer's request and routed to the Compact team through private support triage. Public Service Desk #109 remains the source of record. No applicable license or commercial-use conclusion is claimed while the review is pending.

Links:
- [Service Desk #109](https://github.com/midnightntwrk/servicedesk/issues/109)

## Mithril and bridge research

### Mithril CardanoBlocksTransactions — Ura bridge feedback

Status: **WAITING ON EXTERNAL TEAM**

Ura contributed production bridge feedback to the Mithril CardanoBlocksTransactions rollout, including measured release-preprod proof latency and questions about transaction-body binding and finality configuration. Mithril maintainers responded publicly, and Roy from Teragone invited Ura to discuss its integration experience and roadmap needs. The meeting is not claimed as completed.

Flow: Cardano lock → Mithril certification → Midnight submission → Indexed claim receipt

Links:
- [Public bridge latency feedback](https://github.com/IntersectMBO/mithril/issues/3160#issuecomment-4901140032)
- [Oracle-relay technical questions](https://github.com/IntersectMBO/mithril/issues/3160#issuecomment-4911209129)
- [Roy / Teragone invitation](https://github.com/IntersectMBO/mithril/issues/3160#issuecomment-4992225441)
- [CardanoBlocksTransactions rollout issue](https://github.com/IntersectMBO/mithril/issues/3160)

## Integration assets

### Relay Club integrator kit

Status: **PROPOSED**

- Private / staged SDK and quick-start for capacity → policy → quote → request → receipt.
- Safety boundaries: no secrets, no Keychain, no Preprod live submit in the kit path.
- No public-live or production-submit claim beyond what staged evidence proves.
- External independent handoff test remains pending until completed and recorded.

Links:
- [Partner portal](https://partners.ura.finance/)
- [Related forum note (error 173 / warm path)](https://forum.midnight.network/t/preprod-custom-error-173-wallet-insufficientfunds-could-not-balance-dust-despite-large-dust-balance-now-on-shared-bridge-claimer/1164?u=iampress)

## Footer

Status vocabulary on this page is limited to MERGED, PROVEN, PROPOSED and WAITING ON EXTERNAL TEAM. Claims are grounded in public issues, merged proposals and retained evidence packages. Statuses and claims should be interpreted according to the evidence discipline on this page.