Small Grant: AI Agent plugin (ElizaOS)

Grants Rejected
21

FWIW I did look at GitHub - elizaOS/eliza: Autonomous agents for everyone and I find it an interesting AI agent FOSS project, but everything else discussed here still stands. Additionally I am a very active AI (and agents) user, so it isn’t like im ignorant on these systems either.

@weaver I suggest you get Danger to help you get your pitch to follow guidelines and come back and try again.

Kudos.

22

Thank you very much for your suggestions. Honestly, your advice has been very helpful. Thanks again.

23

Initially, what I wanted to build for this community was the x402 protocol. Imagine if SC could be used not only for payments in data storage, but also extend into other areas of daily life—like creative copyrights. That would be wonderful. But I realized that on a chain like this, implementing x402 is very difficult because it requires writing gasless smart contracts. Then I thought about the TEE in elizaOS, which can enable trustworthy AI Agents—doesn’t that effectively serve as another form of on-chain smart contract? However, elizaOS lacks SiaCoin support, which means I have to do much more development work. That’s why I submitted this proposal: to spare other developers the same difficulties, and to enable my future development of the SiaCoin x402 protocol

24

The biggest flaw everyone makes, as an outsider to the ecosystem, is thinking Sia can do smart contracts.

While there IS a smart contract system as part of consensus, it is NOT a VM. It is probably closer to a more advanced bitcoin scripting system then anything. See Learn | Sia.

So any approach around contracts, tokens, access control, gate-keeping, automation, etc needs to throw all preconceived knowledge out the door on ETH and the smart contract-1st way of doing things and the status quo built up since 2017 and understand how Sia works and what is planned, then ask how that design can be made to work with any ideas you have.

If you want technical input to get help on what can/can’t be done, feel free to DM me on discord as well and I would be happy to chat.

Kudos.

25

Exactly—since there are no smart contracts, I thought about the TEE in ElizaOS and whether it could enable something interesting.

26

If an off‑chain program can be trusted, then what it can do may be equivalent to an on‑chain smart contract.

27

As I stated, if you want to brainstorm the tech aspects, feel free to DM me on discord and I will be happy to help.

Kudos.

1 Like
28

Hi @weaver - welcome to the Sia community and thank you for your proposal.

As @pcfreak30 @CtrlAltDefeat and @Danger mentioned this proposal has some clear gaps and there were some lovely options suggested here for assistance (thanks, folks!).

The technical details of a proposal are key and required, in addition to how this project benefits the Sia ecosystem and supports our mission of user-owned data. I’m going to post a couple of resources here for your reference as you make your edits to your proposal:

  • The website section entitled “Step 2: Cross-check against evaluation rubric”
  • And the Development Guide has been shared before but re-sharing it here to keep it top of mind

As the default questioning from the small grant template included in your proposal indicates, these are questions we do need answered to have this proposal considered by the Committee:

The next Committee meeting is February 3rd so please let me know if you would like the revised proposal to be reviewed before 5pm ET on January 28th.

29

Thank you very much for this helpful community, I really like it. The proposal is being revised, and I will update it soon. Thanks again for the reminder.

1 Like
30

I have revised the proposal. Thank you.

31

I’m not sure whether I should update this proposal directly or use the new proposal: https://forum.sia.tech/t/small-grant-eliza-plugin-sia-revised/1042 I’ve already submitted. Please let me know if there are any issues. Thanks again.

32

Cross-posting my response on the other post here as well for clarity:

Hi @weaver - since this proposal did not go before the Grants Committee, to avoid confusion let’s keep to only this post now featuring your revisions. Please delete the other post.

I’ve also removed the edit I made to the title - I did forget this post hadn’t gone before the Committee yet and made that addition to track changes but I’ve now removed it.

I’ll review this post again and let you know soon if anything else is needed.

33

@mecsbecs Thank you, I’ll note that. Looking forward to your further feedback.

34

Basically, most major public blockchains have provided plugin support for ElizaOS to facilitate community AI Agent development. These are just the merged PRs, in reality, there are far more than this.

35

These links appear to be broken. Please edit before 5pm ET tomorrow Thursday 29th so this proposal can be put before the Committee next week.

36

@mecsbecs Have a good day! I have made these code repositories public. Thank you.

37

Thanks for your proposal to The Sia Foundation Grants Program.

After review, the Committee has decided to reject your proposal citing the following reasons:

  • There is already a similar project in the ecosystem and the Committee does not believe the use case outlined here is materially different.
  • Additionally, all user journeys outlined here are already possible by querying the API.

We’ll be moving this to the Rejected section of the Forum. Thanks again for your proposal, and you’re always welcome to submit new requests if you feel you can address the Committee’s concerns.

38

Thank you for your feedback. I respect the foundation’s decision. The SIA community lacks a platform that can integrate these scattered products, and currently users have a poor experience using them. That’s why I want to build an AI platform. However, it’s clear that the SAI project cannot meet my needs, so other developers and I will not build projects based on it.