Content pfp
Content
@
0 reply
0 recast
0 reaction

dark horsefacts pfp
dark horsefacts
@horsefacts.eth
πŸ“£ Draft spec for miniapp transaction requests. Goals are to 1) let composer actions and miniapps request transactions from the user's wallet and 2) keep this as similar to frame transactions as possible. Feedback is welcome! https://warpcast.notion.site/Draft-Miniapp-Transactions-1216a6c0c10180b7b9f4eec58ec51e55
18 replies
74 recasts
255 reactions

Rob Sanchez pfp
Rob Sanchez
@robrecht
what is currently the difference between a mini app and a composer action? is the only way to open a mini app through a frame atm?
1 reply
0 recast
3 reactions

DegenFans πŸŽ©πŸ”΅πŸ«‚β“‚οΈ pfp
DegenFans πŸŽ©πŸ”΅πŸ«‚β“‚οΈ
@degenfans
Exactly what I need 🀩 Just thinking about the current wallet address, this info we got for frames before we generated the tx.
2 replies
0 recast
3 reactions

Vladyslav Dalechyn /dark pfp
Vladyslav Dalechyn /dark
@dalechyn.eth
Lgtm!
1 reply
0 recast
1 reaction

Ξric Juta  pfp
Ξric Juta
@ericjuta
why would I code a frame over a mini-app?
1 reply
0 recast
0 reaction

Ivy pfp
Ivy
@ivy
LETS GOOOOOOOOOOOOOOOOOOOOOOOOOOO
0 reply
0 recast
1 reaction

MOΞ pfp
MOΞ
@moe
πŸ”₯πŸ”₯πŸ”₯
0 reply
0 recast
1 reaction

dylan pfp
dylan
@dylsteck.eth
this looks sick & this sort of communication between mini apps and clients like warpcast has a lot of potential IMO
0 reply
0 recast
1 reaction

Leo πŸͺ΄πŸŽ© pfp
Leo πŸͺ΄πŸŽ©
@sha25leo.eth
huge!
0 reply
0 recast
0 reaction

Ivy pfp
Ivy
@ivy
looks good to me, error cases covered pretty well
0 reply
0 recast
0 reaction

raulonastool.eth 🎩 🏰 pfp
raulonastool.eth 🎩 🏰
@raulonastool
Have we officially adopted mini-app as the new term (vs. composer action)?!
1 reply
0 recast
1 reaction

shazow pfp
shazow
@shazow.eth
Some feedback on the format: 1. The inner transaction is ultimately JSONRPC 2.0 but outer envelope is kinda similar but not quite. Maybe make everything JSONRPC 2.0? (So we can use the same tooling) 2. requestId is redundant with id in JSONRPC if we go that route. 3. Might be better for the schema to specify a batch of transactions (per JSONRPC2 batch semantics), and just have a list of one by default?
1 reply
0 recast
1 reaction

Fucory pfp
Fucory
@fucory
I would really prefer if the API using postMessage is following the JSON-RPC 2.0 spec
1 reply
0 recast
1 reaction

wasyl pfp
wasyl
@wasyl
I can imagine that other types of actions could use the `postMessage(...)` for beyond transactions and add other basic types of interactivity there
0 reply
0 recast
1 reaction

d_ttang pfp
d_ttang
@ttang.eth
cool
0 reply
0 recast
1 reaction

Garrett  pfp
Garrett
@garrett
πŸ”₯πŸ”₯πŸ”₯πŸ”₯
0 reply
0 recast
0 reaction

dude pfp
dude
@imthedude
Hey, I'm not trying to scam anybody here
0 reply
0 recast
0 reaction

RueπŸ—½ pfp
RueπŸ—½
@rue1776
Love it 🀌
0 reply
0 recast
0 reaction

Shoaib🎩 pfp
Shoaib🎩
@psydeffects
W
0 reply
0 recast
0 reaction