Content pfp
Content
@
0 reply
0 recast
0 reaction

madvi pfp
madvi
@madvi
Currently writing an EIP for a standardized interface for algorithmic functions + context files at the contract level through semantically standardized constructor arguments with immutable variables...goal is to turn smart contracts into adaptive systems learning from interaction histories. Feedback? tinyurl.com/eip8X
3 replies
5 recasts
19 reactions

madvi pfp
madvi
@madvi
new version @lane @austingriffith @publicworks @yassinelanda.eth @sophia /deai @vectornewman @owocki @tomu.eth @df @jpren.eth
1 reply
0 recast
1 reaction

madvi pfp
madvi
@madvi
working on the off-chain side of this also around IPSP where e.g. ceramic can be a great option www.newcoin.org/ipsp for those curious about verifiable points
0 reply
0 recast
1 reaction

kompreni ๐Ÿ…ฑ๏ธ โšก pfp
kompreni ๐Ÿ…ฑ๏ธ โšก
@kompreni
Non revocability: I could see a points contract wanting a decay function. Performance is temporal. Without it, the alternative to decaying one's points would be to inflate everyone else's points? Love the idea of Context Files. Will share more thoughts on this soon.
1 reply
0 recast
1 reaction