본문으로 건너뛰기

7개 문서가 "deploy-action" 태그에 분류되었습니다

모든 태그 보기

CHIP-0035 store-coin spends & delegation

The canonical CHIP-0035 wasm builder constructs every store-coin spend; admin / writer / oracle delegation is the on-chain primitive behind Teams and revocable CI deploy tokens — never hand-rolled.

Deploy from GitHub Actions

Auto-publish your built site or dapp to your existing DIG store on every push with the dig-network/deploy-action — git-push-to-deploy, free PR previews, and a PR comment + GitHub deployment status. Keyless CI auth, no long-lived hub secret.

Deploy keys

Give your CI or an agent a revocable key that can publish new versions of your store — but never your wallet seed, and never the power to change ownership. Issue it once in DIGHUb, drop it into CI as DIGSTORE_WRITER_KEY, and revoke it any time.

For integration developers

완전히 기계가 읽을 수 있는 플랫폼입니다 — OpenAPI/OpenRPC, 체계화된 오류 분류 체계, 실시간 가격 정보, JWKS, 페이지별 JSON, 그리고 타입이 지정된 @dignetwork/dig-sdk를 통해, 사람이 쓴 문장을 한 줄도 스크래핑하지 않고 지갑과 검증된 읽기 기능을 앱에 연결할 수 있습니다.

How do I… integrate DIG into my app?

The shortest path for integrating developers: connect a wallet, read verified content, build a spend the right way, and deploy from CI — using the typed @dignetwork/dig-sdk and the dig RPC, no prose-scraping required.

Webhooks

Register an HTTPS endpoint to be notified when a deployment changes state — queued, building, ready, or error. Each event is signed so you can verify it came from DIGHUb. The event contract — payload shape and signature — is stable; delivery is rolling out.

개념 & 용어집

capsule, store, generation, URN, retrieval key, dig RPC, chia:// 프로토콜, 온체인 앵커링 등 DIG Network의 핵심 엔티티를 한 페이지에 정리한 색인 — 각 항목을 한 번씩 정의하고 관련 심화 문서로 연결합니다.