FilOzone / FilOzone/onramp-contracts
Some UX thoughts
- Dominant language
- Go
- Stars
- 5
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
Feedback from @nicola
- APIs will be changing
- deployment is confusing -- ideally we should have a truffle project here either in place of or next to the foundry project. That might make deployment a bit easier to follow and share. It might even help for my own debugging given how rough its been with foundry so far.
Also wondering about the name xchain for the client cli tool. I have it to evoke "cross chain" but maybe its too generic and or too dry.
other idea list
The more boring:
xstore
cross-store
fil-abroad
fil-sponge
data-sponge
cid-sponge
(I see where cid-gravity came from now, great name)
The more fun:
starfish
nautilus
octopus
argonaut
(all cephalopods are good)
rhizome
mycorrhiza <-- no real takers from quick google search maybe this one. Also `myco` is pretty unused, maybe myco-riza
(now I know where pando came from, another great name)
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no file, test, or entry point; start by reviewing the current Foundry deployment and xchain CLI setup. Clarify whether the desired work is deployment tooling, API changes, or a CLI rename, then define one accepted scope before implementation.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, developer-experience, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100