-
Notifications
You must be signed in to change notification settings - Fork 0
SDKs
Nexa publishes a frozen, language-neutral behavioral contract and shared byte-level conformance vectors. Each implementation maps its native naming conventions to the same ten public operations and shared error model.
The SDK contract and test vectors are canonical. Package registry pages are canonical for currently published package versions.
| Runtime | Package or source | Repository implementation |
|---|---|---|
| Node / TypeScript | npm registry record | sdks/typescript |
| Python | PyPI: nexa-v6-sdk | sdks/python |
| Rust | crates.io registry record | sdks/rust |
| Go | Source module | sdks/go |
| Java / Kotlin | Maven Central artifact | sdks/jvm |
| .NET | NuGet: VihanA.Nexa.V6.Sdk | sdks/dotnet |
The cross-language contract defines these operations:
discovergetRoutesgetRouteverifyFeedrequestPermitMessagerequestPermitresolveExecutionpreviewExecutionbuildExecutionTxgetFillStatus
Go and .NET expose their normal exported naming conventions, with the mapping pinned in the SDK contract.
The shared vectors pin canonical JSON, hashes, recovered signer behavior, Permit messages, request signatures, resolution results, and ABI calldata. The SDK specification README documents the distinct Feed and Permit-request signature boundaries.
SDK conformance does not make local convenience data authoritative. Integrations must still verify the Signed Feed, obtain an Execution Permit, and preserve signing inside their wallet, bot, KMS, or HSM boundary.