FIP (DRAFT IDEA): Casting from Smart Contracts #167
Closed
parseb
started this conversation in
FIP Stage 1: Ideas
Replies: 1 comment
-
Closing due to inactivity |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Motivation:
Make it possible for a contract to cast.
DAO, or composed agent, or as programmable assets; "social media" accounts are needed.
Solution 1 (strict):
Delegate FID Nonce with Content Hash
How: Allow a contract that controls an FID to associate a specific nonce to a cast content hash.
So that:
Any arbitrary signer can trigger the next cast on behalf of an FID provided that the content hash matches the fid specified one.
Solution 2 (generalized):
Delegate an FID Nonce to another FID.
Same effect, but inverse roles: content is arbitrary, signer is specific.
Uses: Monetization. Social apps.
Solution 3 (unlikely):
Add support for EIP1271 signature verification.
Requirements:
Add and enforce mapping between FID nonce and content hash or beneficiary.
TODO:
Understand more how contracts interact with hub.
Beta Was this translation helpful? Give feedback.
All reactions