grjte
@grjte.sh
- https://grjte.sh
- Researcher at @baincapitalcrypto.com exploring programmable cryptography and local-first software
- Experimenting with atproto + local-first software at https://groundmist.xyz
- Researcher at @baincapitalcrypto.com exploring programmable cryptography and local-first software
- Experimenting with atproto + local-first software at https://groundmist.xyz
7/ Check out the details, including a deeper discussion of challenges, a prototype of Bitchat over Wi-Fi Aware, and general notes on cross-platform Wi-Fi Aware implementation
π grjte.sh/bitchat-wifi...
π grjte.sh/bitchat-wifi...
December 23, 2025 at 4:09 PM
7/ Check out the details, including a deeper discussion of challenges, a prototype of Bitchat over Wi-Fi Aware, and general notes on cross-platform Wi-Fi Aware implementation
π grjte.sh/bitchat-wifi...
π grjte.sh/bitchat-wifi...
6/ Wi-Fi Aware would complement BLE as a secondary transport to boost connectivity or enable high-throughput direct messaging. BLE provides a backbone for a ubiquitous baseline mesh. Wi-Fi Aware enables extended range and higher-bandwidth hops when devices both support it.
December 23, 2025 at 4:09 PM
6/ Wi-Fi Aware would complement BLE as a secondary transport to boost connectivity or enable high-throughput direct messaging. BLE provides a backbone for a ubiquitous baseline mesh. Wi-Fi Aware enables extended range and higher-bandwidth hops when devices both support it.
5/ Wi-Fi Aware has challenges: cross-platform support isnβt uniform; pairing flows and asymmetric connection limits complicate mesh formation; hardware support varies.Β But they're not insurmountable, and Wi-Fi Aware could be used today to improve Bitchat and similar networks.
December 23, 2025 at 4:09 PM
5/ Wi-Fi Aware has challenges: cross-platform support isnβt uniform; pairing flows and asymmetric connection limits complicate mesh formation; hardware support varies.Β But they're not insurmountable, and Wi-Fi Aware could be used today to improve Bitchat and similar networks.
4/ Surprisingly, the power cost during discovery was similar between BLE and Wi-Fi Aware, thanks to the optimizations of the Neighbor Awareness Networking (NAN) protocol underlying Wi-Fi Aware. Active transfers consume more energy, but support significantly higher data rates.
December 23, 2025 at 4:09 PM
4/ Surprisingly, the power cost during discovery was similar between BLE and Wi-Fi Aware, thanks to the optimizations of the Neighbor Awareness Networking (NAN) protocol underlying Wi-Fi Aware. Active transfers consume more energy, but support significantly higher data rates.
3/ Wi-Fi Aware throughput is orders of magnitude higher than BLE. In practice, Wi-Fi Aware's range on mobile devices can also be significantly higher than BLE. In tests, we saw ~4-5Γ improvement. Increased range means fewer devices are needed to form a reliably connected network.
December 23, 2025 at 4:09 PM
3/ Wi-Fi Aware throughput is orders of magnitude higher than BLE. In practice, Wi-Fi Aware's range on mobile devices can also be significantly higher than BLE. In tests, we saw ~4-5Γ improvement. Increased range means fewer devices are needed to form a reliably connected network.
2/ Wi-Fi Aware is a wireless discovery and mobile p2p networking standard long-supported on Android (2017) and newly supported on iOS (2025). It lets devices efficiently find each other and set up high-bandwidth Wi-Fi links without an access point.
December 23, 2025 at 4:09 PM
2/ Wi-Fi Aware is a wireless discovery and mobile p2p networking standard long-supported on Android (2017) and newly supported on iOS (2025). It lets devices efficiently find each other and set up high-bandwidth Wi-Fi links without an access point.
1/ Bitchat today uses a BLE mesh for ad-hoc messaging without internet access. BLE is ubiquitous and low-power, but its short range (β10β30 m) and low throughput can limit the real-world reliability and coverage of offline mobile ad-hoc networks that depend on it.
December 23, 2025 at 4:09 PM
1/ Bitchat today uses a BLE mesh for ad-hoc messaging without internet access. BLE is ubiquitous and low-power, but its short range (β10β30 m) and low throughput can limit the real-world reliability and coverage of offline mobile ad-hoc networks that depend on it.
𧡠Could Bitchat have 5x the range and 100x the throughput for the same power expenditure? I explored how Wi-Fi Aware could improve the reliability and throughput of Bitchat and mobile ad-hoc networks in the absence of internet connectivity. #bitchat
π
π
December 23, 2025 at 4:09 PM
𧡠Could Bitchat have 5x the range and 100x the throughput for the same power expenditure? I explored how Wi-Fi Aware could improve the reliability and throughput of Bitchat and mobile ad-hoc networks in the absence of internet connectivity. #bitchat
π
π
2/ Particular thanks to @expede.wtf @patternist.xyz for helpful discussions beforehand and @inkandswitch.com @martin.kleppmann.com @jakelazaroff.com @jessmart.in for referenced work
For an intro to the idea of "programmable cryptography" see gubsheep's excellent essay: 0xparc.org/blog/program...
For an intro to the idea of "programmable cryptography" see gubsheep's excellent essay: 0xparc.org/blog/program...
0xPARC
Supporting application R&D on Ethereum and decentralized platforms.
0xparc.org
July 10, 2025 at 5:03 PM
2/ Particular thanks to @expede.wtf @patternist.xyz for helpful discussions beforehand and @inkandswitch.com @martin.kleppmann.com @jakelazaroff.com @jessmart.in for referenced work
For an intro to the idea of "programmable cryptography" see gubsheep's excellent essay: 0xparc.org/blog/program...
For an intro to the idea of "programmable cryptography" see gubsheep's excellent essay: 0xparc.org/blog/program...
1/ Had a great time on the ZK podcast chatting about local-first and emerging use cases for programmable cryptography (ZK, HE, MPC) with @goblinoats.com @arro.bsky.social @nicomnbl.bsky.social . I'm excited for more exploration here & I'd love to hear ideas from both local-first & prog crypto worlds
The ZK Podcast released an episode on local-first software this week!
@arro.bsky.social and @nicomnbl.bsky.social chat w @grjte.sh & @goblinoats.com about the foundations of local-first architecture, CRDTs and how ZK can be incorporated into these models.
zeroknowledge.fm/podcast/367/
@arro.bsky.social and @nicomnbl.bsky.social chat w @grjte.sh & @goblinoats.com about the foundations of local-first architecture, CRDTs and how ZK can be incorporated into these models.
zeroknowledge.fm/podcast/367/
Local-First with grjte and Goblin Oats - ZK PODCAST
In this episode, Anna Rose and Nico Mohnblatt speak with Goblin Oats from Tonk and grjte from Bain Capital Crypto [β¦]
zeroknowledge.fm
July 10, 2025 at 5:03 PM
1/ Had a great time on the ZK podcast chatting about local-first and emerging use cases for programmable cryptography (ZK, HE, MPC) with @goblinoats.com @arro.bsky.social @nicomnbl.bsky.social . I'm excited for more exploration here & I'd love to hear ideas from both local-first & prog crypto worlds
πI was just talking about your local-first conference talk on a podcast yesterday. I love your new website design too! Fun to engage with & exactly the kind of unique personalized view over PDS data that I was envisioning
June 27, 2025 at 1:41 PM
πI was just talking about your local-first conference talk on a podcast yesterday. I love your new website design too! Fun to engage with & exactly the kind of unique personalized view over PDS data that I was envisioning
Reposted by grjte
π new blog post! i spent a while looking into homomorphically encrypted CRDTs. spoiler alert: they donβt work super well!
(but you should still check it out β i break down what homomorphic encryption is and how it works, and there are lots of explorable explanations along the way!)
(but you should still check it out β i break down what homomorphic encryption is and how it works, and there are lots of explorable explanations along the way!)
Homomorphically Encrypting CRDTs | jakelazaroff.com
Homomorphic encryption allows a computer to run programs on encrypted data. Learn how homomorphic encryption works through interactive examples, build a homomorphically encrypted CRDT and see whether ...
jakelazaroff.com
June 17, 2025 at 1:44 PM
π new blog post! i spent a while looking into homomorphically encrypted CRDTs. spoiler alert: they donβt work super well!
(but you should still check it out β i break down what homomorphic encryption is and how it works, and there are lots of explorable explanations along the way!)
(but you should still check it out β i break down what homomorphic encryption is and how it works, and there are lots of explorable explanations along the way!)
Reposted by grjte
Leaflet Publications: blogging on Bluesky β version 0.1 is here!
β now: make publications, add posts, publish to Bluesky
ποΈ soon: subscribing, commenting & other social features
Try it: leaflet.pub/home
We'd love your feedback & ideas for how we can make this great!
β now: make publications, add posts, publish to Bluesky
ποΈ soon: subscribing, commenting & other social features
Try it: leaflet.pub/home
We'd love your feedback & ideas for how we can make this great!
May 22, 2025 at 3:16 PM
Leaflet Publications: blogging on Bluesky β version 0.1 is here!
β now: make publications, add posts, publish to Bluesky
ποΈ soon: subscribing, commenting & other social features
Try it: leaflet.pub/home
We'd love your feedback & ideas for how we can make this great!
β now: make publications, add posts, publish to Bluesky
ποΈ soon: subscribing, commenting & other social features
Try it: leaflet.pub/home
We'd love your feedback & ideas for how we can make this great!
Reposted by grjte
We built the DMs we wish existed: a messenger that lets you share what you want people to know, and nothing else.
But what if you wanted them to knowβ¦your ATProto handle? π€―
But what if you wanted them to knowβ¦your ATProto handle? π€―
Beta Waitlist β Germ Network
Select \u201CAccept all\u201D to agree to our use of cookies and similar technologies to enhance your browsing experience, security, analytics and customization. Select \u201DManage cookies\u201D toβ¦
www.germnetwork.com
May 20, 2025 at 2:41 PM
We built the DMs we wish existed: a messenger that lets you share what you want people to know, and nothing else.
But what if you wanted them to knowβ¦your ATProto handle? π€―
But what if you wanted them to knowβ¦your ATProto handle? π€―
Reposted by grjte
I've been working on a network-local ATProtocol dev environment that gives me end-to-end production functionality for Smoke Signal, including handle resolution and repository access. Hereβs how I put it together. π§΅
May 14, 2025 at 5:30 PM
I've been working on a network-local ATProtocol dev environment that gives me end-to-end production functionality for Smoke Signal, including handle resolution and repository access. Hereβs how I put it together. π§΅
9/
A personal sync server acts as your local-first PDS, offering local-first benefitsβlike offline access, data ownership, and multi-device supportβwhile enabling the interoperability and flexibility of the AT Protocol.
π Read more: whtwnd.com/grjte.sh/3ln...
A personal sync server acts as your local-first PDS, offering local-first benefitsβlike offline access, data ownership, and multi-device supportβwhile enabling the interoperability and flexibility of the AT Protocol.
π Read more: whtwnd.com/grjte.sh/3ln...
Exploring interoperability & composability for local-first software | grjte
Check out the project at https://github.com/grjte/groundmist-syncCross-posted to https://baincapitalcrypto.com/atproto-for-local-first-interoperability/
This is the third exploration connecting local...
whtwnd.com
May 14, 2025 at 2:45 PM
9/
A personal sync server acts as your local-first PDS, offering local-first benefitsβlike offline access, data ownership, and multi-device supportβwhile enabling the interoperability and flexibility of the AT Protocol.
π Read more: whtwnd.com/grjte.sh/3ln...
A personal sync server acts as your local-first PDS, offering local-first benefitsβlike offline access, data ownership, and multi-device supportβwhile enabling the interoperability and flexibility of the AT Protocol.
π Read more: whtwnd.com/grjte.sh/3ln...
8/
Because your apps are local-first, the user-centric data repo that your personal sync server provides is portable, just like your atproto identity. Update the location of your PSS, and your local-first data will sync in the new data store as you continue to use your apps.
Because your apps are local-first, the user-centric data repo that your personal sync server provides is portable, just like your atproto identity. Update the location of your PSS, and your local-first data will sync in the new data store as you continue to use your apps.
May 14, 2025 at 2:45 PM
8/
Because your apps are local-first, the user-centric data repo that your personal sync server provides is portable, just like your atproto identity. Update the location of your PSS, and your local-first data will sync in the new data store as you continue to use your apps.
Because your apps are local-first, the user-centric data repo that your personal sync server provides is portable, just like your atproto identity. Update the location of your PSS, and your local-first data will sync in the new data store as you continue to use your apps.
7/
With this foundation, any AppView you want to use for interacting with your local-first data can sync and use multiple data types from your PSS without having access to the full PSS. You can do this from any device, even using different services for different devices.
With this foundation, any AppView you want to use for interacting with your local-first data can sync and use multiple data types from your PSS without having access to the full PSS. You can do this from any device, even using different services for different devices.
May 14, 2025 at 2:45 PM
7/
With this foundation, any AppView you want to use for interacting with your local-first data can sync and use multiple data types from your PSS without having access to the full PSS. You can do this from any device, even using different services for different devices.
With this foundation, any AppView you want to use for interacting with your local-first data can sync and use multiple data types from your PSS without having access to the full PSS. You can do this from any device, even using different services for different devices.
6/
This personal sync server (PSS) model can enable local-first interoperability. atproto identity can be used as a user-centric identity for managing and connecting to the sync server. Data can be structured, stored, and permissioned according to a Lexicon definition.
This personal sync server (PSS) model can enable local-first interoperability. atproto identity can be used as a user-centric identity for managing and connecting to the sync server. Data can be structured, stored, and permissioned according to a Lexicon definition.
May 14, 2025 at 2:45 PM
6/
This personal sync server (PSS) model can enable local-first interoperability. atproto identity can be used as a user-centric identity for managing and connecting to the sync server. Data can be structured, stored, and permissioned according to a Lexicon definition.
This personal sync server (PSS) model can enable local-first interoperability. atproto identity can be used as a user-centric identity for managing and connecting to the sync server. Data can be structured, stored, and permissioned according to a Lexicon definition.
5/
This can be fixed by following atproto's lead and making an architectural shift from app-centric sync servers to user-centric sync servers. Instead of local-first apps syncing data to the same server regardless of the user, each user's data syncs to a personal sync server.
This can be fixed by following atproto's lead and making an architectural shift from app-centric sync servers to user-centric sync servers. Instead of local-first apps syncing data to the same server regardless of the user, each user's data syncs to a personal sync server.
May 14, 2025 at 2:45 PM
5/
This can be fixed by following atproto's lead and making an architectural shift from app-centric sync servers to user-centric sync servers. Instead of local-first apps syncing data to the same server regardless of the user, each user's data syncs to a personal sync server.
This can be fixed by following atproto's lead and making an architectural shift from app-centric sync servers to user-centric sync servers. Instead of local-first apps syncing data to the same server regardless of the user, each user's data syncs to a personal sync server.
4/
In the local-first context, data interoperability is challenging partly because it lacks atproto's data model separation. It also lacks user-centric identity, schema standardization, a permission system, and a discovery mechanism, all of which facilitate apps sharing data.
In the local-first context, data interoperability is challenging partly because it lacks atproto's data model separation. It also lacks user-centric identity, schema standardization, a permission system, and a discovery mechanism, all of which facilitate apps sharing data.
May 14, 2025 at 2:45 PM
4/
In the local-first context, data interoperability is challenging partly because it lacks atproto's data model separation. It also lacks user-centric identity, schema standardization, a permission system, and a discovery mechanism, all of which facilitate apps sharing data.
In the local-first context, data interoperability is challenging partly because it lacks atproto's data model separation. It also lacks user-centric identity, schema standardization, a permission system, and a discovery mechanism, all of which facilitate apps sharing data.
3/
For data interoperability across services, we need legibility as well as discoverability and accessibility beyond the original app. atproto enables this by combining the Lexicon system with data model separation where user-centric data repos are separated from AppViews.
For data interoperability across services, we need legibility as well as discoverability and accessibility beyond the original app. atproto enables this by combining the Lexicon system with data model separation where user-centric data repos are separated from AppViews.
May 14, 2025 at 2:45 PM
3/
For data interoperability across services, we need legibility as well as discoverability and accessibility beyond the original app. atproto enables this by combining the Lexicon system with data model separation where user-centric data repos are separated from AppViews.
For data interoperability across services, we need legibility as well as discoverability and accessibility beyond the original app. atproto enables this by combining the Lexicon system with data model separation where user-centric data repos are separated from AppViews.
2/
The latest Groundmist experiment explores how a personal sync server can function as a local-first data store, mirroring the role of an atproto Personal Data Server (PDS) and building on the lexicon schema system's foundation to enable interoperability over local-first data.
The latest Groundmist experiment explores how a personal sync server can function as a local-first data store, mirroring the role of an atproto Personal Data Server (PDS) and building on the lexicon schema system's foundation to enable interoperability over local-first data.
May 14, 2025 at 2:45 PM
2/
The latest Groundmist experiment explores how a personal sync server can function as a local-first data store, mirroring the role of an atproto Personal Data Server (PDS) and building on the lexicon schema system's foundation to enable interoperability over local-first data.
The latest Groundmist experiment explores how a personal sync server can function as a local-first data store, mirroring the role of an atproto Personal Data Server (PDS) and building on the lexicon schema system's foundation to enable interoperability over local-first data.
1/
In the 1st Groundmist experiment, we used atproto as a publishing target for data drafted privately in a local-first context. In the 2nd, we explored atproto's Lexicon schema system as a legibility foundation for describing how to interact with various local-first data.
In the 1st Groundmist experiment, we used atproto as a publishing target for data drafted privately in a local-first context. In the 2nd, we explored atproto's Lexicon schema system as a legibility foundation for describing how to interact with various local-first data.
May 14, 2025 at 2:45 PM
1/
In the 1st Groundmist experiment, we used atproto as a publishing target for data drafted privately in a local-first context. In the 2nd, we explored atproto's Lexicon schema system as a legibility foundation for describing how to interact with various local-first data.
In the 1st Groundmist experiment, we used atproto as a publishing target for data drafted privately in a local-first context. In the 2nd, we explored atproto's Lexicon schema system as a legibility foundation for describing how to interact with various local-first data.
𧡠The AT Protocol shows the power of a personal data store. All of our public atproto data is easy to find and access. We can interact with it flexibly in myriad ways and combinations.
Wouldn't it be nice to do the same for our private and collaborative data? π
Wouldn't it be nice to do the same for our private and collaborative data? π
May 14, 2025 at 2:45 PM
𧡠The AT Protocol shows the power of a personal data store. All of our public atproto data is easy to find and access. We can interact with it flexibly in myriad ways and combinations.
Wouldn't it be nice to do the same for our private and collaborative data? π
Wouldn't it be nice to do the same for our private and collaborative data? π