Open bmann opened 2 years ago
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
This issue now has a funding of 10.0001 FIL (656.71 USD @ $65.67/FIL) attached to it as part of the fission-suite fund.
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
Workers have applied to start work.
These users each claimed they can complete the work by 265 years from now. Please review their action plans below:
1) sksb2180 has applied to start work _(Funders only: approve worker | reject worker)_.
Fission webnative includes things needed to do this task. I'll start it asap after confirmation.
Learn more on the Gitcoin Issue Details page.
@jtsmedley Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days
Sorry @jtsmedley, I snoozed this, don't know if I can make this not happen.
That's a bummer. I'm still going to build the tooling out and may use fission for key transfers but the data access layer seems like it may be better handled separately right now and then my tool can just sync the public CID of the encrypted database into your public store. That way it's compatible with Fission but also capable of being standalone with your own estuary.
Just to be clear! Totally going to bounty you on this, just that I don't know if I can do anything about this auto-bot :)
Yeah, there's a dag-add so that it can be just added that way. No rush!
Jason S wrote in the Filecoin #arg Slack channel:
We'd love to support this! We want to see a demo app that implements saving to IPFS.
The example app should:
Instead of the linked repo in the quote, this might also be an excuse to extend the absurd-sql example project with webnative support.
You might also make use of Fission's WNFS versioning features to do something interesting.