Bringing rise to Data 3.0 and other indexing-related shenanigans

Main

indexing

Will be pitching /indexing tomorrow alongside the rest of the Codebase cohort in their Demo Day 🫡

Come join! https://lu.ma/codeabaseS3pitchday

Deck here: https://pitch.com/v/indexing-co-vwaz2y

honored to have placed 3rd! 🔺

genuinely owe it all to the team making up for my [lack of] pitch skills

5 promising startups just wrapped S3 of Codebase, Avalanche's flagship incubator, culminating in a live Virtual Pitch Day. 

Each project had the opportunity pitch to a panel of distinguished judges for $500k in grand prizes!  

Let's see the results 👇
https://t.co/L1sDd4yHRg

honored to have placed 3rd! 🔺

genuinely owe it all to the team making up for my [lack of] pitch skills

https://x.com/avax/status/1936167927272886541?s=46&t=pXqR2LRF3Lqnfa7JlhoJig

Farcaster

I have now open sourced /intelligent

The codebase is now free for everyone to use and build on top of. No attribution required. 

Few notes:
1. I've vibe-written a detailed Readme in both Frontend & Backend Repos
2. You might need to replace a few services but both repos are well-structured and organized for you to deep dive.
3. If you do stumbleupon any secrets, the services are already dead, so don't worry. I have scrubbed it anyways!

Frontend: https://github.com/tanishqsh/intelligent
Backend: https://github.com/tanishqsh/intelligent-backend

Here are some major services I used to run this:
Farcaster Raw Data: Indexing by @runninyeti.eth 
Database: postgres on GCP
Data Cache Layer: Firebase
Metadata: Moxie API [Needs replacement] and @Neynar
Job Scheduler: BullMQ + Redis
Frontend Deployment: Vercel
Backend Deployment: Heroku

A free gift: I had created an employee (custom GPT) with Intelligent's schema and data last year to plan and write code faster. Sharing that custom employee in comments below.

Feel free to ping me anytime in case of any doubts!

Long live /intelligent, long live Farcaster

tbd on timing, but aiming to get this setup as a public good via /indexing asap

devFC

in case you're wondering. yes pipelines with indexingco

we built a lightweight CLI for indexingco as we use webhook pipelines across client projects and management via bash scripts was cumbersome :D

@runninyeti.eth said we'll be able to ship more farcaster webhook related things soon. watch out

in the meantime we use indexingco for onchain webhooks

wen retro grants?

(seriously though, this epic!)

Will be pitching /indexing tomorrow alongside the rest of the Codebase cohort in their Demo Day 🫡

Come join! https://lu.ma/codeabaseS3pitchday

Deck here:

avalanche

I'm increasingly convinced @avalanche culture is the best of web3 right now. 

Unbothered. Moisturized. Happy. In their own lane. Focused. Flourishing.

And not on FC.

Enjoyed chatting open data at 🔺Summit

Come find me at the next event!

With p̶r̶i̶c̶e̶s̶ innovation on the rise, some reminders:

1) "steady lads" isn't in our vocabulary; our infra is backed by real assets

2) @monad was supported weeks ago; some say we can see the future

3) our customers invest more in memecoins; with data infra solved, they get back to what makes them unique

Just added Litecoin for funsies - what's next?

Just added Litecoin for funsies - what's next?

https://docs.indexing.co/networks/litecoin

I'll be speaking at the /avalanche Summit🔺 on May 21st on how to Love Your Data Again

Reach out if you'll be in town!

FarCon NYC

the-arena

Building /indexing, the next data stack

This week we:

- found a way to break a 200tb RAID device; all is well 🫡 
- pushed some updates to our docs; more guides coming soon!
- cut over to snapchain for existing indexing -> paves the path for more upgrades soon(ish)

See you all at /farcon-nyc this week! 👋

Building /indexing, infra for the distributed world

Last week was mostly R&D:
- Began planning a Neighborhood for token data -> more on that in coming weeks
- Deeper SQLite work for universal queues
- Cleanup work for asset tracking across Aptos, Sui, and Solana

Happy Easter 🐰

Web1 = my compute
Web2 = their compute
Web3 = our compute

Join us

At https://t.co/cxJAjf7WAo, we're building the future of data accessibility.

The thesis remains simple:

Web1 = my compute
Web2 = their compute
Web3 = our compute

Idle compute is *everywhere* and we're on a mission to make it useful.

Web1 = my compute
Web2 = their compute
Web3 = our compute

Join us

https://x.com/indexingco/status/1912965322141057516

SimpleHash and Reservoir shutting down are perfect examples why indexing.co is built different and perfect for web3.

Builders demand more from their data solutions. APIs are remnants of legacy web2 architectures. Consumer and defi apps are only as unique as their data - builders need focused, transformed data delivered directly to them. 

This is what we offer. Our customers save >70% on their data infra while focusing on what makes them unique.

Reach out if you're ready to upgrade your data stack - we're committed to building in public and my dm's are always open 🐇

Building /indexing, distributed infra for open data

This week we:
- Found a 15x improvement in what we lovingly call "The Void"
- Continued ^ our march towards bare metal -> eventual on-prem
- Onboarded /sui 
- Explored ephemeral, distributed stream architecture with early adopters (for cases like Base's "flash blocks", MegaETH's "mini blocks", Cast Protocol's gossip'd stream, etc)

Excited to announce that /indexing has joined Avalanche Codebase to begin protocolizing our infra. The thesis remains simple:

- Web1 = my compute
- Web2 = their compute
- Web3 = our compute

While "crypto" has been a clear first use case for these distributed primitives, it certainly won't be the last. Idle compute is *everywhere* and we're on a mission to make it useful.

Whether on-chain or off-chain, the promise of Web3 is in permissionless, limitless access to data. @indexingco believes in a future where data flows freely and is fully controlled by the end person, business, or even autonomous agent accessing it.
https://t.co/3h0jR7Cz72

Excited to announce that /indexing has joined Avalanche Codebase to begin protocolizing our infra. The thesis remains simple:

- Web1 = my compute
- Web2 = their compute
- Web3 = our compute

While "crypto" has been a clear first use case for these distributed primitives, it certainly won't be the last. Idle compute is *everywhere* and we're on a mission to make it useful.

https://x.com/avax/status/1907464995790545090

Building /indexing, distributed infra for open data

This week we shipped:
- JITI template support for `tokenTransfers` for Filecoin and Substrate chains
- Snapchain (Cast Protocol 😉) support; we'll be ready as soon as the switchover happens
- Optimizations for customer backfills -> beginning a full revamp to bring that in-house next
- Got into [REDACTED] to help build [REDACTED] by the end of May -> will be casting from /london next week 🇬🇧

Congrats on making it to the weekend!

https://theweekend.lol/