Developing in the open

As we bring the core components of Fetch.AI to life, we’ve been working largely in private and then snapshotting our work across to public repositories at relatively regular intervals. Now that our test network is live, and the key components are all in the right place, we’re changing that. We’ve taken the leap and made our primary ledger repository public¹, so you can see all the work we do each and every day. It’s an exciting moment, and in the coming weeks, we’ll move the remainder across: almost 200 repositories covering the OEF, mobile apps, agent SDKs and more.

As we take this step, we’ll be releasing a detailed analysis of our code, to enable you to see how we compare with others and get an interesting and useful perspective on the work that we’re delivering.

To support developers and the community, we’re introducing tagged releases. This enables you to run everything without any hiccups. We have a dedicated team refining and creating documentation so that it’s super easy for you to run a Fetch.AI node, develop synergetic contracts, build and work with the OEF and connect an agent. It’s everything you need to realise the full potential of Fetch.AI.

We are incredibly excited to be where we are now, setting the scene for the coming months and years.

Finally, don’t forget: airdrops for those who fork our projects and push contributions to them are a sure thing. We also have opportunities to contribute to our decentralised apps, native apps (mobile and desktop) and contracts. All of this is happening monthly this year as part of our competition incentives and I can’t wait to talk more about that soon!

- Josh (internal champion of autonomous agent development.)

1) And don’t worry, the old public ledger is present as a read-only repository called ledger-archive