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.

Sign up for GitHub

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

Jump to bottom

Governance Horizon #297

Open
3 of 14 tasks
gavofyork opened this issue Nov 12, 2021 · 1 comment
Open
3 of 14 tasks

Governance Horizon #297

gavofyork opened this issue Nov 12, 2021 · 1 comment
Labels
I6-meta A specific issue for grouping tasks or bugs of a specific category. T1-FRAME This PR/Issue is related to core FRAME, the framework.

Comments

@gavofyork
Copy link
Member

gavofyork commented Nov 12, 2021 •
edited
Loading

On auctions/slots:

  • Advanced scheduling systems
    • Parathreads (PAYG cores)
    • Core rotation (1 core between multiple chains)
  • Slot flexibility
    • Multi-period slot auctions (3 month, 6 month, 12 month, 3 year, 5 year)
    • Improve future auctions: 10% DOT down-payment required for reservation only. Rest to be provided prior to slot start time, at pain of slash and slot loss.
@gavofyork gavofyork changed the title Liquid Governance Governance New Horizon Nov 28, 2021
@gui1117
Copy link
Contributor

gui1117 commented Dec 7, 2021

I have this PR paritytech/substrate#10159 based on paritytech/substrate#10356
It creates a pallet to whitelist some calls with origin and execute those whitelisted call from another origin

@joepetrowski joepetrowski mentioned this issue Apr 5, 2022
Closed
@gavofyork gavofyork changed the title Governance New Horizon Governance Horizon Mar 19, 2023
@juangirini juangirini transferred this issue from paritytech/substrate Aug 24, 2023
@the-right-joyce the-right-joyce added I6-meta A specific issue for grouping tasks or bugs of a specific category. T1-FRAME This PR/Issue is related to core FRAME, the framework. and removed J1-meta labels Aug 25, 2023
claravanstaden pushed a commit to Snowfork/polkadot-sdk that referenced this issue Dec 8, 2023
@musnit @denalimarsh @vgeddes
Full Beefy MMR Relay chain -> Ethereum working with e2e tests (parity…
3c0a974 
…tech#343)

* fixz

* Add subscribe script

* Add MMR proof+leaves

* add offchain relay workers

* decode mmr proofs

* update readme

* fix config

* update README (paritytech#297)

* improve get authorities

* get more data in script

* Add commitment log

* tests use incentivized channel id

* relayer log more

* test query epoch

* generate lightclientbridge contract bindings

* implement parachain chain for testing

* add keypair getter to eth connection

* add parachain to relay

* update go.mod, go.sum

* drop relayer from start-services script (testing)

* add lightclientbridge to truffle migration

* send initial verification tx to eth contract

* BeefyCommitmentInfo type, msg builder methods

* add BeefyBlockDelay to config

* implement WriteCompleteSignatureCommitment

* integrate beefy listener, poll eth blocks + events

* add beefy chan, update chain interface for compile

* generate validatorregistry contract

* generate mmr proof offchain

* sync header before polling eth blocks

* listener compile

* update config

* generate mmr proof onchain + verify val registry

* implement WriteCompleteSignatureCommitment

* add block hash helper function

* writer test

* update go.mod/go.sum

* deploy val registry contract with params

* rename parachain to relaychain

* integrate latest contracts

* rename contract to PolkadotRelayChainBridge

* query onchain beefy authorities

* in-memory database

* refactor substrate listener

* refactor ethereum listener/writer

* update chain interface

* refactor relay.go

* bump go.mod, go.sum

* remove checks in polkadotrelaychainbridge contract

* delete relaychain package

* delete relaychain package

* fix pending nonce conflict

* update tests

* implement random seed for completion tx

* remove duplicated fields on Beefy/BeefyItem

* handle edge case: use intended completion block

* fix conditional statment

* parachain, relaychain abstractions

* remove validatorregistry contract for now

* initial ethereum revisons

* remove relayconn from chain interface

* update mmr -> merkle

* update configuration

* update parachain tests

* fix relaychain init error

* update parachain test endpoints

* close relaychain lister, database

* use database.stop

* fetch BLOCK_WAIT_PERIOD directly from contract

* remove block number from tx sent log

* update beefy naming conventions

* normal channels

* only process events from our node

* move authorities to types file

* remove extra param

* update contracts to latest

* comment out bridge verification checks

* clean up

* wait until block is finalized to send complete tx

* refactor eth writer cron job

* update writer test

* start relayer with start-service script

* ignore relaychain init channels

* combine msgs/BEEFY msgs write loops

* clean up

* minor fixes

* update polkadot version

* Fix event forwarding

Co-authored-by: Denali Marsh <[email protected]>
Co-authored-by: Vincent Geddes <[email protected]>
helin6 pushed a commit to boolnetwork/polkadot-sdk that referenced this issue Feb 5, 2024
@zjb0807 @sorpaas
Fix estimate_gas (paritytech#297)
1e092f7 
* fix estimate_gas

* format

* format

Co-authored-by: Wei Tang <[email protected]>

Co-authored-by: Wei Tang <[email protected]>
jonathanudd pushed a commit to jonathanudd/polkadot-sdk that referenced this issue Apr 10, 2024
@svyatonik @bkchr
Fix (workaround) for "cannot read property 'toFixed' of null" (parity…
aa90d16 
…tech#297)

* fix (workaround) for NaN CPU usage

* cargo fmt --all
github-merge-queue bot pushed a commit that referenced this issue Dec 4, 2024
@lexnv
chore: Update litep2p to v0.8.3 (#6742)
5ca7267 
## [0.8.3] - 2024-12-03

This release includes two fixes for small memory leaks on edge-cases in
the notification and request-response protocols.

### Fixed

- req-resp: Fix memory leak of pending substreams
([#297](paritytech/litep2p#297))
- notification: Fix memory leak of pending substreams
([#296](paritytech/litep2p#296))

cc @paritytech/networking

---------

Signed-off-by: Alexandru Vasile <[email protected]>
lexnv added a commit that referenced this issue Dec 4, 2024
@lexnv
chore: Update litep2p to v0.8.3 (#6742)
75fe332 
## [0.8.3] - 2024-12-03

This release includes two fixes for small memory leaks on edge-cases in
the notification and request-response protocols.

### Fixed

- req-resp: Fix memory leak of pending substreams
([#297](paritytech/litep2p#297))
- notification: Fix memory leak of pending substreams
([#296](paritytech/litep2p#296))

cc @paritytech/networking

---------

Signed-off-by: Alexandru Vasile <[email protected]>
Krayt78 pushed a commit to Krayt78/polkadot-sdk that referenced this issue Dec 18, 2024
@lexnv @Krayt78
chore: Update litep2p to v0.8.3 (paritytech#6742)
27ecc5f 
## [0.8.3] - 2024-12-03

This release includes two fixes for small memory leaks on edge-cases in
the notification and request-response protocols.

### Fixed

- req-resp: Fix memory leak of pending substreams
([paritytech#297](paritytech/litep2p#297))
- notification: Fix memory leak of pending substreams
([paritytech#296](paritytech/litep2p#296))

cc @paritytech/networking

---------

Signed-off-by: Alexandru Vasile <[email protected]>
dudo50 pushed a commit to paraspell-research/polkadot-sdk that referenced this issue Jan 4, 2025
@lexnv @dudo50
chore: Update litep2p to v0.8.3 (paritytech#6742)
ab3a1ae 
## [0.8.3] - 2024-12-03

This release includes two fixes for small memory leaks on edge-cases in
the notification and request-response protocols.

### Fixed

- req-resp: Fix memory leak of pending substreams
([paritytech#297](paritytech/litep2p#297))
- notification: Fix memory leak of pending substreams
([paritytech#296](paritytech/litep2p#296))

cc @paritytech/networking

---------

Signed-off-by: Alexandru Vasile <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
I6-meta A specific issue for grouping tasks or bugs of a specific category. T1-FRAME This PR/Issue is related to core FRAME, the framework.
Projects
Runtime / FRAME
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
4 participants
@gavofyork @juangirini @gui1117 @the-right-joyce