1import{u as s,j as e}from"./index-Cb08R15b.js";const a={title:"Overview",description:"undefined"};function i(r){const n={a:"a",code:"code",div:"div",h1:"h1",header:"header",li:"li",p:"p",strong:"strong",ul:"ul",...s(),...r.components};return e.jsxs(e.Fragment,{children:[e.jsx(n.header,{children:e.jsxs(n.h1,{id:"overview",children:["Overview",e.jsx(n.a,{"aria-hidden":"true",tabIndex:"-1",href:"#overview",children:e.jsx(n.div,{"data-autolink-icon":!0})})]})}),` 2`,e.jsxs(n.p,{children:["Rust-focused documentation for the Circles protocol, mirroring the original TypeScript SDK docs. Code samples use the Rust crates (",e.jsx(n.code,{children:"circles-types"}),", ",e.jsx(n.code,{children:"circles-pathfinder"}),", ",e.jsx(n.code,{children:"circles-rpc"}),", ",e.jsx(n.code,{children:"circles-profiles"}),", and helpers)."]}),` 3`,e.jsxs(n.p,{children:["Status: ",e.jsx(n.strong,{children:"alpha, but no longer read-only"}),`. Querying, pathfinding, event 4decoding, transfer planning, invitation/referral planning, and native 5runner-backed writes are available today. Full TypeScript parity is still in 6progress, especially around browser-hosted execution and some service/auth 7polish.`]}),` 8`,e.jsxs(n.ul,{children:[` 9`,e.jsx(n.li,{children:"What is Circles? Personal and group currencies on a trust graph."}),` 10`,e.jsx(n.li,{children:"Crates: types, pathfinding, RPC/query helpers, profiles, transfers, SDK, and runners."}),` 11`,e.jsx(n.li,{children:`Ready today: pathfinding, querying, event decoding, type-safe data structures, 12direct and path-based transfer planning, replenish flows, group-token 13mint/redeem planning, invitation/referral helpers, and native EOA / Safe 14execution.`}),` 15`]}),` 16`,e.jsxs(n.p,{children:["See ",e.jsx(n.code,{children:"/circles-sdk"})," for SDK structure and ",e.jsx(n.code,{children:"/reference"})," for API details."]})]})}function d(r={}){const{wrapper:n}={...s(),...r.components};return n?e.jsx(n,{...r,children:e.jsx(i,{...r})}):i(r)}export{d as default,a as frontmatter};
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.