You must be able to run ss or lsof as root to gather the node-s PID in their ouput,
as I HIGHLY DO NOT RECOMMEND running a node and this script as root.
The easiest way is just add simmilar entries as the following into the /etc/sudoers or create a file under /etc/sudoers.d/
The /etc/sudoers example, but pls ensure that the path to those files are correct:
User_Alias SPO=spo,ahtn,shmn
| {-# LANGUAGE DataKinds #-} | |
| {-# LANGUAGE DeriveAnyClass #-} | |
| {-# LANGUAGE DeriveGeneric #-} | |
| {-# LANGUAGE DerivingStrategies #-} | |
| {-# LANGUAGE TemplateHaskell #-} | |
| import Control.Applicative (Applicative (pure)) | |
| import Control.Monad (void) | |
| import Language.Plutus.Contract | |
| import qualified Language.Plutus.Contract.Constraints as Constraints | |
| import qualified Language.Plutus.Contract.Typed.Tx as Typed |
USE EVERYTHING BELOW AT YOUR OWN RISKS!
A Cardano community member has lost one word of his the 12-words menomic/"recovery phrase", and he would like to recover his wallet from these 11 words.
It is be possible based on the following assumptions:
11! * 1550 = 60bn tries i.e. 1700 years:(.
DISCLAIMER: The following example is based on the Chapter 4.3 and 5.6 in latest design spec and the Ranking Specification. But it seems that the ranking mechanism specified in the Design Specification, and explained below, is not fully implemented and/or enabled or I missed some of the details of the spec (more realistic assumption). Also, I have not checked what is the difference between the design doc and the current implementation of the haskell code to check if there is any difference, or I misinterpreted some of the both sources (design doc, haskell code). Anyway, I will check the code when I have some spare time.
UPDATED 09/23/2020
The pool ranking in wallet is based on the stake the user intend to delegate and the expected `
This guide's chapter targets the pool operators for getting their head around of current Shelley's Network stack until P2P (Governor with DeltaQ) arrives. It also provides some networking practices, for setting up a staking pool environment.
Disclaimer: All the Information in this gist, only applies to the currently implemented network stack of Haskell Shelley, and might be inaccurate or even completely wrong. The Author cannot be held responsible for any consequences after/before using any information from this gist, therefore, you acknowledge that you are USING THEM AT YOUR OWN RISK.
This guide's chapter targets the pool operators for getting their head around of Shelley staking. To fully understand the staking mechanism we need to define and interpret the following key concepts:
