Restrict access to our development networks
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- blockchain, security
Research direction
No files, tests, or entry points are named. Start by reviewing the issue's DevNet and QANet access problem and the listed Telegram suggestions, including deployment restrictions, ops keys, balance resets, and Stellar testnet bridging. Done requires an agreed access-control approach that confines development-network resources to team members.
Written by the indexing model from the issue text.
Description
Currently, we are indulgent by letting anyone access our grid resources (DevNet, QANet) if he knows how to access them.
This practice has resulted in uninvited access to our development resources, and we have received reports of machines and public IP addresses being rented by unauthorized individuals.
To mitigate these issues, we need to restrict access to our development networks, confining the accessibility to only our team members.
Suggestions made so far on a recent TG discussion:
-
restrict deploying on DevNet from the tooling. Or
-
restrict holding TFTs on devnet for only team members by
- switching from using known development substrate keys (Alice, Bob, etc) and using an ops key instead.
- resetting balances including Alice (can be done by force transfer tokens to known team members).
in this case, we will also need to restrict TFTs on stellar testnet as it can be bridged to tfchain.
Let's discuss this in more detail. Additionally, please share any other ideas you may have.
- Dominant language
- No language data
- Stars
- 13
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from threefoldtech/grid_wiki
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
threefoldtech/grid_wiki#1602 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
threefoldtech/grid_wiki#1601 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
threefoldtech/grid_wiki#1600 ·
-
genexplorer Open
Difficulty 5/5 Over a week Newbie friendliness 15/100
threefoldtech/grid_wiki#1599 ·
-
type_story
threefoldtech/grid_wiki#1598 · 3 comments · 2 assignees ·
All issues in threefoldtech/grid_wiki
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
blinklabs-io/bursa#904 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
rust-bitcoin/rust-bitcoin#6908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Merit-Systems/x402scan#1215 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Uniswap/default-token-list#2585 ·