oasisprotocol / oasisprotocol/oasis-core

debug enclaves flag should be consensus backed

Open
#2,285 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
369
Forks
151
Avg merge
1d 3h
Merged PRs (30d)
6

Description

In light of #965 the allowance of debug enclaves should not be set per node via CLI as now, but then driven by network consensus.

For implementation details, see Yawning's comment https://github.com/oasislabs/oasis-core/pull/2262#issuecomment-543574869

Estimated cost: 1 sprint

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with issue #965 and Yawning's implementation comment on pull request #2262, then trace how the debug-enclave allowance is currently supplied through the node CLI. The work is done when that allowance is driven by network consensus rather than set independently per node; the payload provides no file or test names.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
blockchain
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.