How to bidirectionally replicate data between DNAs?

Hey I have a friend who wants to contribute some tax accounting standards stuff to HoloREA’s ecosystem… she has dived in to Corda a bit so I was hoping I could share your doc with her in order to get her up to speed, provided I tell her not to circulate? How do you feel about that kind of thing per that document specifically?

I think that’s fine, esp for the sake of HoloREA :slight_smile:

https://miro.com/app/board/o9J_kx0H2NA=/

The craziest validation I’ve seen so far- https://github.com/holo-rea/holo-rea/issues/93

This is interesting! Is this only true within the same DNA (I would expect), or across DNA’s as well?

Also want to say thanks @pospi and @pauldaoust for this great thread – I read with interest, followed links, and learned a lot.

2 Likes

Only within the same DNA.

@pauldaoust and I developed a pattern for zome modularisation via this process that seems to be holding up well for me in Holo-REA. One of the requirements there is to split library code and zome internals neatly into related crates, such that you can use defs inside the co-located zome itself but interact with its storage layer by using lib in either that zome, or any others local to the DNA.

1 Like

What’s the current status on this conversation? Is this where Module Patterns came from?

Is no one building organelles and organs?

Is gossip redundancy being used for backing up source chains?