Community FAQ
Short answers to the most common questions from users, providers, and node operators. For deeper dives, see the linked sections.
General
What is Sylan?
A decentralized API marketplace. Providers list APIs and set prices (Pay‑Per‑Call or Subscription). Consumers pay in SYL; off‑chain nodes fetch data, and on‑chain contracts verify provider signatures, reach consensus, and settle payments.
Which networks are supported?
Testnet: Polygon Amoy (80002). Mainnet target: Polygon (137). Addresses live on Architecture → Addresses & ABIs.
Do I need SYL to use Sylan?
Yes. Consumers pay in SYL. You can acquire test SYL from the team for Amoy, or from supported listings/exchanges once mainnet is live. See Quickstart.
How does Sylan keep data trustworthy?
Providers sign EIP‑712 snapshots; nodes submit them; the chain verifies signatures, enforces freshness windows, tallies votes, and finalizes results. See Concepts → Data Integrity and Consensus.
For Consumers
How do I make a one‑off request?
Approve SYL to APIEscrow, then call lockForCall(apiId, requestHash, expiresAtMs). Watch events through to Settled/Refunded. See Quickstart and Architecture → Events.
What’s a requestHash?
A keccak256 of your canonical JSON payload so everyone agrees on the same bytes. It anchors escrow to exactly one request. See Concepts → Data Integrity.
Can I get a refund?
Yes—if consensus fails (e.g., NoQuorum or InactiveAPI), PPC requests are refunded automatically by escrow.
How do subscriptions work?
You pay once per period; funds are allocated immediately to Provider/NodePool/Platform. Per‑call requests under a subscription don’t lock funds. See Concepts → Plans & Pricing.
For Providers
How do I list an API?
Register an apiId in AccessRegistry, set your plan (price/duration/limit), descriptor (URI + contentHash), and providerSigner (EIP‑712 key). See Contracts → AccessRegistry.
What do I sign?
Not raw payloads. You sign a compact Snapshot: { apiId, seqNo, providerTs, ttl, contentHash }. Nodes carry it to consensus. See Concepts → Consensus.
Where do I host results?
Anywhere—IPFS or HTTPS—but integrity is via the contentHash in your snapshot. Nodes/UIs fetch by pointerURI and verify the hash.
Can I change prices or BPS?
Yes—changes affect future purchases/locks only. Existing PPC locks keep their original snapshot; active subscriptions are unaffected until renewal.
For Node Operators
What hardware do I need?
Commodity servers are fine (2–4 vCPU, 8–16 GB RAM). You’ll run an HTTP client, a signer/verifier, and a relay to submit snapshots. See Node docs (coming soon).
Do I need to stake?
If NodeRegistry is enabled, yes—stake ≥ minStake to be Active and eligible. Mismatching votes can be slashed; honest voters may receive rewards. See Contracts → NodeRegistry.
How many votes finalize a request?
Set by quorum in APIConsensus. If quorum isn’t met before expiry, the deadline path kicks in.
Security & Privacy
Do you store raw data on‑chain?
No—only hashes/IDs. Payloads live off‑chain; integrity is enforced by hashes and signatures.
What happens if a provider signs conflicting data?
Consensus emits ProviderEquivocation. Operators should investigate; governance may penalize repeat offenders. See Concepts → Security.
Who can upgrade contracts?
Proxies are UUPS and owned by a multisig. Upgrades follow a public runbook. See Contracts → UUPS Upgradeability.
Token & Sale
What is SYL used for?
Payments (escrow), staking/rewards, and ecosystem incentives. See Contracts → Sylan Token.
Will there be a sale?
A PresaleContract exists for capped/whitelisted sales with claim/refund mechanics. Timing and terms will be announced separately. See Contracts → Presale.
Troubleshooting
My PPC request never finalized.
Check: API active, expiresAtMs not too short, nodes online, and that your requestHash was canonicalized the same way as nodes. Review events under Architecture → Events.
Finalization failed with InactiveAPI.
The provider deactivated the API before finalization. PPC funds are refunded; subscriptions follow policy (off‑chain).
permit keeps failing.
Confirm you’re signing the right chainId, verifyingContract (SYL proxy), and your wallet’s nonce. See Contracts → Sylan Token.
Still have questions?
Open a discussion on the repo or reach out via the community channels listed on the homepage.