You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently a URL is linked to a specific aggregator / portal like this https://blobid.walrus/<PATH>.
It would be cleaner to transition to a separate protocol for a client to talk to an aggregator.
For example, IPFS handles this by having an ipfs:// protocol that clients redirect to whatever way they have to get IPFS blobs.
We should do something similar with walrus sites.
Example schemes:
wsite://
walrus://
OR
Use the web+walrus and web+blob protocol registrations.
Component
portal
Code of Conduct
I agree to follow this project's Code of Conduct.
The text was updated successfully, but these errors were encountered:
Tzal3x
changed the title
[Major Feature]: Transition to a new url scheme to match the walrus protocol
Transition to a new url scheme to match the walrus protocol
Dec 12, 2024
Description
Currently a URL is linked to a specific aggregator / portal like this
https://blobid.walrus/<PATH>
.It would be cleaner to transition to a separate protocol for a client to talk to an aggregator.
For example, IPFS handles this by having an
ipfs://
protocol that clients redirect to whatever way they have to get IPFS blobs.We should do something similar with walrus sites.
Example schemes:
wsite://
walrus://
OR
Use the
web+walrus
andweb+blob
protocol registrations.Component
portal
Code of Conduct
The text was updated successfully, but these errors were encountered: