Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IPFS backend(s) #9

Open
treyzania opened this issue Jan 14, 2018 · 1 comment
Open

IPFS backend(s) #9

treyzania opened this issue Jan 14, 2018 · 1 comment

Comments

@treyzania
Copy link
Contributor

treyzania commented Jan 14, 2018

Use a backend such as IPFS to actually store and distribute blocks/etc. to other nodes.

Downsides:

  • Relies on external software, which could be automated depending on the situation.
  • Not as cool.

Upsides:

  • Slightly less targetable.
  • Easier.
@treyzania
Copy link
Contributor Author

Something like what might end up happening.

pub enum Address {
    Internal(sig::Hash),
    Ipfs(blob::SmallBlob)
}

I'm not sure how useful internal addresses are going to end up being with this. We might have to separate the notions of block addresses from addresses of artifacts/segments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant