The problem Machu Picchu solves

• For the humanitarians, with the blockchain and IPFS, the cost of managing the data of persons in need is reduced, the reporting to donors is auditable, the design of helper programs is more accurate. No more silos.
• Each person in need will own the personal data and is incentivised to keep them data accurate and relevant, as if they were the portfolio of an artist that would be consulted by casting agents. Self-help.
• The data is open to all organisations that address this segment: humanitarians (WFP, UNICEF, red Cross...), micro-finance institutes, development agencies, insurers, world-size buyers (Nestlé, Danone, Coca-Cola), input sellers (Bayer, Syngenta, Corteva...). Everybody would pay the owners a small fee (tokens) to access the data. This would be on top of their existing Voucher & Cash Assistance programs. Open + Integrated with existing
• Big names will have their own tokens, small players will use a common accepted token, for example Machu Picchu's. Open + Decentralised
• The persons in need would ultimately use a DEX to exchange their tokens from various origins into a bundle of one type of tokens of their choice, to be able to convert them into fiat for a specific use, to keep the bank conversion overhead low. Inclusive Finance + banking the unbanked
• It contributes to SDG 1(No Poverty) and SDG 17(Partnership for the goals). By its tokens, it supports directly SDG 2(Zero Hunger), SDG 3(Good Health & Weel-Being), SDG 4(Quality Education), SDG 5(Gender Equality) and SDG 10 (Reduce Inequalities).

Challenges we ran into

We thought that porting our demo from Ethereum to Celo would be straightforward, and our plans was to focus rather on adding IPFS and Textile. But it took us longer than foreseen to align our work methods. We are now a very well aligned team. We had to drop the database part, but we'll come back next year with more hacks to add to Machu Picchu.

Fortunately the Celo people were very reactive and supportive.