Skip to content

Instantly share code, notes, and snippets.

@ilap
ilap / jc.env
Last active October 17, 2019 10:48
JC
#
# Install: Add to the profile
#
# Usage: jc stake-get
#
alias jc='_() {
if [ -z "$*" ]
then
echo '\''usage: jc [Rest commands]
- stake get: Shows the current delegation info

Keybase proof

I hereby claim:

  • I am ilap on github.
  • I am ilap (https://keybase.io/ilap) on keybase.
  • I have a public key ASDiVDzi9NTlM-daMMe8wYkGarcITtk01vpk1KQ6wKWw2go

To claim this, I am signing this object:

@ilap
ilap / byron_yoroi_address_migration_to_shelley_v3.sh
Last active December 15, 2019 21:55
Byron's Yoroi address migration to Shelley v3 address.
#!/bin/bash
# Get the spending key of your Yoroi address for signing the spending.
# At repl.it/repls/IndolentWarmheartedDehardwarization
# FORK IT FIRST!!!!!!!!!!!
# And replace the
# MNEMONICS="your mnemonics" with yours and then
# from `console.log(address.to_base58());``
# to `console.log(key_prv.to_hex());`
KEY=""
@ilap
ilap / shelley_config.md
Last active January 30, 2020 00:08
Jormungandr Config Explanation
# P2P Section explanation
p2p:
  # This is the node's `identifier` in the Poldercast topology. This should be unique and 
  # deterministic (which is not the case in jormungandr) in the poldercast network, and
  # it's highly recommended to be set, because a random `id` is generated on every node restart otherwise.
  # So, we introduced a free sybil attack against to the Poldercast's nodes in default (if it's not set).
  # It simply means that the number of nodes (node ids /w address) in the poldercast increasing by every node's restart
  # and just forgotten very slowly. Therefore, currently there are ~80K node entries in the topology, 
  # which can be one of the reasons the nodes block/slow sometimes.
@ilap
ilap / layman_covid19.md
Last active April 15, 2020 22:46
Layman's explanation of COVID19
@ilap
ilap / fnf_exc3.md
Last active May 22, 2020 06:15
Shelley FnF Exercise 3

Shelley Stakepool Pioneers Exercise Sheet 3

#!/bin/bash

# FnF Exercise 3
# 1. KES Mechanism (for rotating operational cert)
# - Generate the cold (offline) key pair that is used to evolve the operational certs (using new hot KES keys periodicaly).
# - Generate the hot KES (offline/online) key pair for generating the cert.
# - Generate the operational cert (offline) based on the evolved KES and VRF key.
@ilap
ilap / fnf_ex2.md
Last active May 22, 2020 06:25
FnF Exercise 2

Excercise 2

  1. Build simple transactions using the basic transaction mechanism;
  2. Sign transactions and confirm that the transaction is complete;
  3. Submit transactions to the Pioneer Blockchain;
  4. Verify that the transactions have been processed by inspecting the addresses that they have been sent to.

Build transactions

#!/bin/bash
@ilap
ilap / setup_node_mon.bash
Last active May 23, 2020 18:21
Setup Shelley Monitoring (cardano-node)
#!/bin/bash
#---------------------------------------------------------------------
# File: setup_shelley_monitoring.sh
# Created: 2019/10/17
# Creator: ilap
#=====================================================================
# UPDATES:
# - 21/05/2020: Updated to the `cardano-node` i.e. Haskell Shelley
#
# DESCRIPTION:
@ilap
ilap / htn_exercise5.md
Last active May 24, 2020 22:16
Shelley Stakepool Pioneers Exercise Sheet 5
@ilap
ilap / htn_exercise4.md
Last active May 25, 2020 01:21
Shelley Stakepool Pioneers Exercise Sheet 4

Shelley Stakepool Pioneers Exercise Sheet 4

Key Types and their functions

  • Node Keys (Cold, Hot, VRF)
    • Cold key: operator's offline key pair with cert counter for new certificates.
    • Hot KES key: operator's hot KES key pair.
    • Block signing key: operational VRF key pair, it participates in the "lottery" i.e. right to create and sign the block for the specific slot.
  • Address (Payment, Staking etc.) keys
  • Payment key: single address key pair (usually for generating UtxO address)