joeldw
Joined 4 years ago
Joined 4 years ago
Understanding is really the measure of utility. I suspect that an average human's intelligence is similar to one 100 years or even a century ago, and thus our ability to discover new theorems and proofs. The difference is the understanding. We not only have the last thousand years of discovery, but also the compaction, categorization, education, tutorials, etc, that allowed us to learn it effectively in a few years or decades of academia.
AI is accelerating the discovery part, but the _understanding_ part is just as vital for true progress.
Who incentivizes the data availability is more of an application-layer question; in this case it could be the game publisher itself or maybe a consortium of players. I've tried to build these options as much as possible into the contract layer as opposed to the scaffold protocol itself.
- A WS + WebRTC mesh
- A request/response protocol incentivizing the closest or most efficient peers to respond to requests
- A WASM environment ensuring deterministic execution and supporting contract composition
- Collateralization around responses, ensuring invalid responses have amortized negative value
- A consensus and UTXO layer, focused on low-latency, low-finality micropayments (for request incentive and collateral), using WASM compute as the weight metric
The idea came out of me wondering a few years ago why a multiplayer game couldn't simply be run on the player's machines without a central server. It has grown since, but the focus has remained on low-latency and log(N) state consensus (unlike a blockchain).
It's wrapped up as a single fetch() method, mostly mirroring the browser's native fetch(). There's a lot more I could say; I love working on it and discovering elegant solutions to the problems that pop up. I'm hoping to release a prototype in a few weeks/months. If you're interested in trying it out, let me know (joel at scaffold.io); I'd love to have some other eyes on it.
- We save companies money on their cloud spend (AWS and GCP), and are building additional services around security and cost visibility.
- We are profitable and growing extremely quickly ($1m to $10m ARR last year, 500+ customers) and are growing our team to match.
- We're looking for engineers who are passionate about building elegant, scalable products and systems. We are a small team (6 engineers, ~20 total); you will have ownership and will work closely with the business and customers.
- Python backend, typescript frontend
- https://www.ycombinator.com/companies/pump-co, or reach out directly at joel@<domain>