Skip to content

Update introduction.mdx #41

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 7, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions introduction.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -6,10 +6,10 @@ Polybase is a privacy preserving decentralized database, built on zk-STARKs. We

**At a high level, Polybase is a NoSQL-like database, with validation rules written in a JavaScript like language. The SDK is similar to Firestore and Supabase.**

Polybase is better than using a centralized database like Firebase, Postgres or Supabase because you can encrypt data using wallets for "self sovereign data" and verifiably query Polybase from smart collections (coming soon).
Polybase is better than using a centralized database like Firebase, Postgres or Supabase because it has built-in web3 permissions. You can do row-level token gating and wallet-based permissions. Additionally, you can encrypt data using wallets for "self sovereign data" and verifiably query Polybase from smart collections (coming soon).

Polybase is better than storing data on-chain because it's 1000 to a million times cheaper than on-chain storage. For example, storing 1MB on Ethereum costs around $10,000.

**Blockchains are not built for scalable structured data storage so we built Polybase to combine the best attributes of web2 databases and blockchains.**

You can [get started](/get-started) in under 5 minutes.
You can [get started](/get-started) in under 5 minutes.