Holochain Forum

Modularity Hackalong | 'Lego-blocks' for the new economy 🔧 ⚙ 🙂

Hello all. This week we’re going to explore what it’s like to use economic building-blocks for your community. Topics will include

  • How modularity works across multiple DNAs
  • GraphQL, and how you can design your UI using these tools
  • What lego-blocks are available/being designed (Holo-REA, Mutual Credit and Sacred Capital libraries)
  • Where CRISPR tools are relevant

When : Thursday, June 11, 9am SGT/11am AEST/1am UTC/6pm PST (US: June 10)
Where : Zoom Room ; Calendar Invite
Who is this relevant for: anyone looking to leverage these themes. You could be a dev building in a modular fashion. Or a ‘power user’ with limited dev skills who is stitching together a community or app with basic technical tools.

For those who missed the last session with the Holo-REA CRISPR Mash-up, you can watch the recording here.

Thanks, Sid.
PS: If you’d like to receive the calendar invite leave a comment below or DM me and I’ll add you to the recurring event.
PPS: More about Modularity here


Looking forward to Weekly Hackalong for PowerUser, especially interested in learning where CRISPR Chimera has reached, so that as promised to @philipbeadle we could get some Training Content going by end of June - early July.

1 Like

Here’s the video. Good conversation today about modularity in the context of GraphQL APIs, discussing aspects of CRISPR that could be relevant for modularity, what an implementation of Mutual credit might look like in Holo-REA versus the standalone Mutual Credit App and which approach to choose, and an intro to some reputation libraries.

PS: If you’ve got suggestions for improving the conversations, or ideas for themes you’d like to cover feel free to DM them in, or add them to this thread.


Can you please share Guillem’s remote bridge link @pospi posted in the hackalong chat? Thanks!

1 Like

That was quick @lchang, here are all the links that were shared.

|09:47:54| From pos pi : https://github.com/holochain-open-dev/remote-bridge
|09:51:40| From pos pi : https://www.artbrock.com/docs/map-of-currency-spec-space.pdf
|09:52:02| From Sid : https://github.com/sacredcapital/Reputation-likes

1 Like

Thank you very much, @sidsthalekar
As always, great session & discussion!

1 Like

Hi, your links are broken because you added a useless pipe at the end.

Done! Thanks @pegaltier - copied them straight out of the Zoom text file.

1 Like

Client side framework of HoloREA
@pospi builder behind HoloREA

Services like Holo REA implementing ValueFlow GraphQL schema making it plug-able with a completely different backend (commonspub) without any UI changes

  • UI leverages GraphQL to query Holochain, thus authoring UI components comes with a perspective of tight bind to data

  • buildGraphQL , GQLtester framework to query and test synchronously.

  • Uses ZomeFunction bindings for HoloChain connection

Why GraphQL? GraphQL vs REST API design architecture

HoloREA uses GraphQL to improve reliability in interacting with holochain DNA, such that there is a tight schema binding with hard breakage between front-end and back-end.

  • Tester method inside GraphQL method, has eliminated need for global setconnection method, as the tester method contains the conductor uri enclosed within itself. This change helps in creating multiple user profiles (having their own conductor running on separate port) with separate graphql apis, tested at once.

  • ConductorUri embeded inside Tester method allows for each user to have their own GraphQL without requiring a global state

  • Top Level GraphQL API connects holochain by generating value flows implementations

  • Resolver functions are simple exports of resolver function to holochain as GraphQL, these object are then applied to holorea schema

  • GraphQL module contains all the UI components to connect with HoloChain in one place

DNA identifier are just hAPPs that holoREA pulls out of holochain with zome function bindings, which gets called back as part of the Resolver Callback functions such as Query Functions to retrieve information such as ( Agents, Types of Resources, Resources ), though the function is the same but the internal logic depends on what is being queried for

  • holochain doesnt have different security environment between browser and holochain signed code, thus entire client side graphQL binds directly into holochain

  • GraphQL API could opens up possibilities of connecting with other tools and services for integrations, which is all made possible by GraphQL tooling.

HoloREA and ChimeraCRISPR comparision

  • ChimeraCRISPR and HoloREA have their own distinct vision. Where ChimeraCRISPR allows people to bring different stuff from other people in the form of PreBuilt Building Blocks with possibility of authoring and customizing those pieces.
  • ChimeraCRISPR install looks like your Whole Organizations Digital Token, with possible low level artifacts that can be created to meet specific needs of your organization, with backend and frontend components kept in Chimera signed holochain, which during runtime deployment bring those DNAs together assembled in the specific manner i.e. the culture you want as part of your organization.
  • ChimeraCRISPR is pursued from Compile time terms as to what goes into DNA, while HoloREA is approaching form Run time terms, which is dynamic and changes between DNAs.
  • ChimeraCRISPR UI functions calls holochain code directly, thus opening up possibility of code organization modularization that would have to be considered as his application scales.
  • While HoloREA is using GraphQL api’s which has rich schema language.