borodutch
@warpcastadmin.eth
gm, blockchain + ipfs + opengsn is the perfect match for blockchain as backend and database it's fast, permissionless, customizable, user-friendly upkeep costs of product build like this? $0 and it gets more performant the more users use it, as opposed to the classic backend/frontend pair
7 replies
0 recast
0 reaction
borodutch
@warpcastadmin.eth
ipfs is used to store data (including media and metadata) and spa frontend for blockchain any l2 would suffice but going with polygon is ok opengsn allows you to cover gas fees (for polygon they are miniscule) but when you run out of $100 that you deposited for gas fees, users can still pay for gas fees
1 reply
0 recast
0 reaction
borodutch
@warpcastadmin.eth
you can add ens to it and all of a sudden you have a url for the spa frontend — the more people use the link, the more ipfs nodes cache the front-end, the faster the first load becomes
0 reply
0 recast
0 reaction
Yakov K.
@purplenoodlesoop
Instructions unclear, made an SSR app on PostgreSQL
1 reply
0 recast
0 reaction
Razberry
@razberry
Do you find that ipfs works well as a practical db? As in speed, querying, relations & tables, etc?
1 reply
0 recast
0 reaction
Justin Hunter
@polluterofminds
How do you suggest people manage IPFS infra and availability? Just start small with it running on a raspberry Pi or something more complex?
1 reply
0 recast
0 reaction
Kiren Srinivasan
@kiren
Cool web3 use case: The backend you don’t have to pay for
1 reply
0 recast
0 reaction
moreReese
@morereese
@perl
0 reply
0 recast
0 reaction
