Fundamentals

Start with the question. Then choose the interface.

A focused reading path from the Builder Notes library.

A blockchain application is easier to build when its boundaries are clear. These guides explain shared data models and the choices behind request-and-response reads, resource-oriented APIs, and subscriptions. Begin with the multichain overview to define a narrow first feature. Continue with the transport comparison to decide how that feature should receive updates and recover after a gap. The emphasis is on application design: preserve network identity, name the limits of your data, and choose a pattern you can test. These articles do not assume that one provider or one message format makes all chains interchangeable.