cal 🎾 (zk/acc)
@calummoore
Followers
13,051
Following
661
Media
146
Statuses
770
cto @payy_link , using zk for you know, privacy.
UK
Joined March 2009
Don't wanna be here?
Send us removal request.
Explore trending content on Musk Viewer
Elon
• 531845 Tweets
Congreso
• 451432 Tweets
Garland
• 222400 Tweets
Colômbia
• 214532 Tweets
Game 3
• 92466 Tweets
Brazil
• 91563 Tweets
$COOKIE
• 87965 Tweets
FANDOMS CONTRA A PL 1904
• 73920 Tweets
Golpe de Estado
• 70961 Tweets
イーロン
• 68012 Tweets
欄非公開
• 63496 Tweets
プライバシー
• 56956 Tweets
自分の投稿
• 52266 Tweets
Jim Jordan
• 48327 Tweets
Seleção
• 46438 Tweets
#CriançaNãoÉMãe
• 46401 Tweets
自分のポスト
• 46201 Tweets
自分のツイート
• 43360 Tweets
Blade
• 39413 Tweets
DISCORDO TOTALMENTE
• 36509 Tweets
تويتر
• 34443 Tweets
O VAR
• 26524 Tweets
生存確認
• 26298 Tweets
ブックマーク
• 22801 Tweets
Alisson
• 19715 Tweets
Midori
• 17539 Tweets
누가 맘찍
• 17329 Tweets
Rodrygo
• 16036 Tweets
#いいね非公開
• 15710 Tweets
#AEWDynamite
• 14333 Tweets
バイエルン
• 11582 Tweets
Pulisic
• 10331 Tweets
Pinned Tweet
our zk-rollup proof system (used on our live rollup)
10
14
187
Developers, it's still early in web3. If you get in now, you'll be an expert when it becomes mainstream.
19
57
422
Developers: now is the best time to learn web3, but it can be overwhelming. Here's some tips to get started.
A thread 🧵
35
67
308
zk-proofs: I can prove to you I know where Wally is, without showing you where Wally is…
15
36
176
if the proof is not generated on the phone, its not a zk proof
11
8
147
A bit more detail… we’re a privacy preserving decentralised database, built on zk-STARKs. Here’s how it works…
3
4
58
utxo state model is not privacy preserving by itself, but its hard to be privacy preserving without a utxo model
2
3
60
Our decentralised network of validators store only the hash for each record, so the underlying data and indexing can be stored anywhere, such as on the client (for user owned data), Filecoin/Arweave (decentralised), or even S3 (centralised 😬). The choice is yours.
3
3
42
Database collections have validation rules, which enforce the rules on adding data to the database. These rules can be written in Polylang (our js-like language), and we compile that to zk-STARKs for you.
2
3
39
tldr; if you use our SDK, you can consider Polybase to be a NoSQL-like database, with validation rules written in a JavaScript like language.
2
2
38
We also provide our own storage and indexing which has a similar syntax to Firestore (NoSQL), so that everything works out of the box. But it’s pluggable, so we hope others will create new plugins that support GraphQL, aggregation, search and more.
1
1
31
When you want to make database writes, our client SDK (mobile or browser) creates the proof based on the validation rules to ensure the change is valid. The network checks the proof, and if valid updates the record hash.
1
1
27
2
5
30
(technically, I need to commit to the original image, and then reveal 32 other locations based on the hash, so you know its not some random other image)
1
1
24
@th0r4g
A database isn’t by definition centralised. It’s a place to store data. We use zk-STARKS to allow data to be stored on the client or in a decentralised store.
3
1
21
See, here he is. And I’ve given you (almost) zero knowledge about where he might be.
1
0
18
1. Don't worry if not everything is 100% web3 at the beginning. Build something, you can always make it more web3 later.
4
0
20
@payy_link
zk circuits are now open source
🚀 run in under 3 seconds on an iPhone
🪄 UTXO proofs are under 2.8KB
✅ proofs are compatible with EVM
audited by
@kalos_security
and running on the Payy Network mainnet
💽
📖
0
2
20
Founders that don’t drop what they are doing to build a new AI thing will be the ones that are successful
1
1
11
@th0r4g
Some of it does, some of it doesn’t. Building the decentralised web, requires decentralised compute and data.
1
0
17
2. Build the frontend in a language you already know, you can interact with (deploy, call, read) smart contracts and the blockchain in almost any language.
2
0
16
First up, a company harvesting blockchain data for ML. Going to be pretty challenging when everyone starts using zk 😅
1
1
12
8. For solidity, consider using
@0xPolygon
instead of
@ethereum
for your first project, it's 100% compatible but with lower fees. For rust, try
@Polkadot
.
3
2
16
@jamafouino
You can either encrypt data, or if super private you can store on the client. Our storage is pluggable, so there will be lots of different options. Our state tree means, that you can generate a proof for any data in the tree, without revealing the data.
1
0
14
3. Smart contracts are essentially a set of lambdas/functions, with the bonus that any code that updates state, does so in a transaction safe way. Each smart contract has its own state/data that these functions can update. Anyone can view a contracts state.
3
0
14
Cloud CPU is so incredibly slow
Google Cloud (360 cores) = 0m31.359s
MacBook Pro (8 cores) = 1m27.161s
Just a casual $11k a month 😂
0
0
9
10. There are a bunch of other developer tools to help with developing your smart contracts locally on your machine - here are two great options:
@HardhatHQ
-
Foundry - -
4
2
13
5. An account on the blockchain is a kind of identity, but you don't have to be limited to one (similar to how you can have multiple accounts on Twitter). Each account has a private key, that is used to sign transactions to prove they are legit. Never share your private key.
2
0
12
@payy_link
for android coming out this week 🔥
why did we hold out on releasing Android?
⚠️ massive difference in device screens and capabilities
⚠️ janky backup system (so we can backup your private key)
⚠️ compiling our zk-circuits to android was epic challenge
0
1
11
17. Or if you'd prefer not to pay, this is another great course (although I haven't taken it myself):
1
2
12
9.
@openzeppelin
can help reduce the boilerplate for your solidity smart contracts. It's a library you can import that handles lots of common use cases (e.g. ERC-20 tokens, NFTs, permissions).
1
0
12
@kirill_ylide
That will be possible, storage is pluggable and we’ll be creating an integration with arweave and filecoin
1
0
12
@payy_link
is actually 2 things
- wallet - reference impl with incredible app ux for private payments
- network - open (anyone can build on) L2 zk-rollup to enable private payments
1
3
10
16. If you like online courses, then I have personally taken this course, and found it to be very helpful -
2
0
9
@Lakshay_enth
You could use it to build a Google Drive like app, we’re actually building a bunch of different demo apps, so I’ll add that to the shortlist
2
0
10
7. It's actually best practice to keep your contract code short and concise, as the more code, the more open to vulnerabilities it is.
Remember, anyone can read your smart contract, and people actively look to exploit them.
1
0
10
woke up from a dream last night and legit thought I had the best idea ever… was so excited
1
1
6
6. You can interact with smart contracts in any language, but to create your own you will need to learn either solidity (similar to JS) or rust. Don't worry, smart contract code is usually only a small part of your dapp, and the language is easy to pick up.
2
0
10
18. If you want to understand more of the core concepts of the blockchain and different protocols, then I recommend this YouTube channel -
1
1
10
You can read the unrolled version of this thread here:
1
0
9
4. You can add any write permissions you like to your smart contract using code, by simply checking the account key that is calling the function, and then using code to decide whether that account is allowed.
1
0
9
11. For live, use
@AlchemyPlatform
or
@POKTnetwork
for your connection to the blockchain. Don't try and host your own node.
2
0
9
15. To deploy your smart contract, you need to buy your blockchain's currency, and have access to the public and private key to the account that you deposit to.
Avoid buying from Coinbase, as that will mean you have to pay twice (once to buy, and again to transfer to a wallet).
3
0
7
14. Use
@graphprotocol
if you need to query data from the blockchain at speed (especially if that data is historic).
2
0
8
13. Use
@ipfs
+
@Filecoin
or
@arweaveteam
for web3 file/data storage (e.g. where you would normally use AWS S3)
2
0
9
@Rutuja06332171
Yes, so you can set the rules in a way that prevents them from being ever changed. Or you can make the owner a DAO with on chain governance for updates.
1
0
8
@AikonMishima
@polybase_xyz
@tableland__
@polybase_xyz
we’ve designed our database from the ground up to be scalable and provable using zk-proofs. Tableland permission model is based on calling an Ethereum smart contract, so it comes with similar downsides.
tldr; similar goal, very different tech.
1
0
9
Yes, we’re hiring for a senior frontend engineer
Yes, you will be rejected immediately if you apply using chat-gpt
5
1
9
@sidgandhi_xyz
@RobinhoodApp
@0xPolygon
@TrustWallet
@CoinbaseWallet
@MetaMask
Collecting wallets from now on instead of NFTs
15
0
2
@SHUDOG123
The separation enables better privacy (for applications that need it), it means you don’t have to reveal the underlying data at all. It also means developers can choose the best storage/index for their requirements. Different options for different use cases.
1
0
8
halo 2 is the best zk framework
0
0
8
excited to be giving a talk at privacy reunion part 2 by
@privacyguardia
on April 24th
"Preserving privacy in p2p payments" - it's actually harder than it looks, lots of ways you can accidentally drop privacy if not careful
1
2
8
@payy_link
the link is the money, we create an ephemeral private key for each "note" you send to someone, that's all they need to spend the money.
"Preserving privacy" talk
@privacyguardia
3
1
8
Exciting times!
🎉 Thrilled to announce, Polybase raised $2 million in pre-seed funding to build the default database for web3 devs
Thank you to our investors, including
@6thManVentures
@protocollabs
@OrangeDAOxyz
@alumniventures
@NGC_Ventures
@CMTDigitalLtd
@upfrontvc
12
40
75
1
1
6
every crypto wallet has the same UX, and we wonder why we can't get mass adoption
0
2
8
@W3Hidayath
Right now it’s NoSQL, but we have plans to allow modular plugins that will support SQL, ML and more
1
0
8
0xAF657A8Fa036bcc99AC3cCd5b7fFa4AaddFBE501
addresses are scary and confusing for non-crypto folks, we need to remove them to onboard the next B
2
1
8
Kinda sad that most rollups are centralised, is it really that hard to add a lil bit of consensus
0
0
8
sorry, but this is what the table should actually be
@EliBenSasson
suggests "validium" as a clearer name for plasma-with-snarks (aka zk rollup but with offchain data). That is:
12
44
191
1
1
7
Frontend Development:
HTML: 3 hours
CSS: 5 hours
JavaScript: 6 hours
Fix scroll issues: 23 hours
0
0
5
Me auditing every web3 contract I use to make sure it won't steal my money. 😅
1
0
7
payments is only the beginning
if you love our payments UX, you are going to love our DeFi UX
0
2
7
19. Also checkout this blockchain demo to get an intuitive understanding of how blockchain works -
1
1
7
recursion/aggregation is the biggest bottleneck for zk, that's where all our effort needs to be
0
1
7
This has to be the most beautiful disgusting things AI has ever created.
0
0
3
If you want to know where to start with web3, check out this thread:
Developers: now is the best time to learn web3, but it can be overwhelming. Here's some tips to get started.
A thread 🧵
35
67
308
0
2
7
💡 web3 idea: take any exiting web2 business and re-build it in web3.
(worked for a lot of early internet companies)
1
0
7
@Alwaysl63264798
@govendible
I would say it’s more around cross chain private identity, than structured data storage and querying. Looks like a cool project 🔥
2
1
6
payments need an app specific chain, so we can push blockchain/zk performance to its limits
general purpose is great for everything else
0
0
6
"every payment shouldn’t be an investment decision"
don't be the guy who spent 1 BTC on a burrito
stay safe, use stablecoins
0
0
6