Content
@
0 reply
0 recast
0 reaction
Dan Romero
@dwr.eth
Description - Electron app that is cast only (no feed) - Tutorial for installing app, importing a signer and connecting to a Hub in 30 minutes - Open source, MIT license, code on GitHub - First entry that replies to this cast that has proper tutorial for hello world cast Amount $500 USDC Deadline 2 weeks @bountybot
7 replies
1 recast
41 reactions
dylan
@dylsteck.eth
On it ser!!!
5 replies
0 recast
4 reactions
jp 🦊🎩
@jpfraneto
what is your take on what "importing a signer and connecting to a Hub" means? if accounts X mnemonic and i want to write messages to the protocol through a hub that i have access over localhost, how can that be done? im stuck there https://warpcast.com/jpfraneto/0xd9aff333
1 reply
0 recast
0 reaction
dylan
@dylsteck.eth
have the electron app up and running and this is what I’m working on rn! my thought here is you’re creating the signer and the flow for creating the signer & casting happens through a designated hub (matters more for casting)
2 replies
0 recast
1 reaction
jp 🦊🎩
@jpfraneto
so the hub needs to issue a signer associated with that specific account, even if that account is the "manager" of the hub on the .env that hubble reads? i don't understand how this thing works enough to figure that out
1 reply
0 recast
0 reaction
dylan
@dylsteck.eth
ahh my bad, I kinda confused things with my explanation lol. - you create the signer with a flow that relies on Warpcast deep links and IIRC this doesn’t require hub interaction from the developer - you use the signer to then post hub messages(like a cast)
1 reply
0 recast
0 reaction
dylan
@dylsteck.eth
^ you can make a signer directly from a hub but that requires the account's mnemonic, which isn't usually the ideal UX for a client/app
1 reply
0 recast
1 reaction