{"title": "Ame Network", "logoImg": "bafkreighoaw3j7mro6mwkie7s4lcw2lfcfhxb7add2eqmxdohgu4peo6ju", "website": "https://ame.network/", "bannerImg": "bafkreibhaeegc6wwuqaujfmyac4pfcnw6j2qac5ndggoejswwnavq43ua4", "createdAt": 1722305702066, "userGithub": "HelloRickey", "credentials": {}, "description": "\n## What is Ame Network\n\nThe future is onchain, and the composability of onchain applications is just like the modularity of the chain. Ame is a composable social network, allowing users to customize and combine different social functions and tools according to their interests, needs and preferences. This hyperstructure brings diverse and rich social experiences to users on the chain.\n\n## Impact\n\n### Permissionless and autonomous\nThe contracts of the composable social network are deployed on various decentralized networks, adopt an open architecture and are completely open source. Developers do not need to apply for any API key or access permissions, and can freely use their imagination to expand in any dimension. This is like Facebook and Twitter directly opening up the highest permissions to their servers and databases to you.\n\nUsers in social networks also have absolute autonomy to decide the functions and display formats of your social applications. No one can unilaterally control your account and data. The development of the network will also be determined by users, core infrastructure contributors, and developers of community components.\n\n### Component as a service\nComponents are a concrete representation of composability, and each component represents a service or function. Every social software has some core functions. In fact, we only use these 20% core functions 80% of the time. Composable social networks componentize these core functions, and users can combine different social functions and services to achieve a more personalized social experience. Our goal is not to build a completely decentralized Twitter. We can use multiple components to combine into an onchain Twitter.\n\n### Interoperable interface\nThe interoperable interface standard is to facilitate all parties to read and write onchain social component data, just like HTTP, any client and server can send POST, GET, PUT, and DELETE to implement CRUD on resources on other servers. Similar standards can also be used to package functions in smart contracts. When the client makes a request to the contract, it indicates the type and method of operation to be taken, and the corresponding method in the contract returns a response. And the two contracts can also interoperate according to standards.\n\n## Useful Links\n- [Ame Netowrk Website](https://ame.network/)\n- [Ame Network Introduction](https://www.youtube.com/watch?v=ldSopYOPukA&t=48s)\n- [Ame Twitter](https://twitter.com/0xAmeNetwork/)\n- [Composable Social Network](https://mirror.xyz/0xBFDc0906313Dec9DD0f38D5867060627e3ba5C9E/vp4ueV7TF8c4JzT5fL5Y4wz6CTn6aVTQBdnOoGhbHPA)\n- [Ame Javascript SDK](https://github.com/HelloRickey/ame-sdk)\n- [Ame Components Scan](https://scan.ame.network)\n- [How to build a social component](https://mirror.xyz/0xBFDc0906313Dec9DD0f38D5867060627e3ba5C9E/9bxItBA2muUtOzH8PLdRCIjcBw1lpvmm-im1HqtF2GY)\n- [Request Method Types(EIP-7654)](https://eips.ethereum.org/EIPS/eip-7654)", "logoImgData": {}, "bannerImgData": {}, "projectTwitter": "0xAmeNetwork"}