The easier way to manipulate [ECC][1] key-pairs and signatures is via the perl module [Crypt::PK::ECC][2].
Below is a simple example of code for
- creating the key pair ([secp256k1][3]) :
eckeygen.pl
- signing and verifying a message :
signature.pl
This is a way to redirect a domain name the IPFS version of the site
#!/usr/bin/perl | |
#BEGIN { if (-e $ENV{SITE}.'/lib') { use lib $ENV{SITE}.'/lib'; } } | |
# usage: | |
# ipfs key export -o /dev/stdout DPKI | perl DHkeys.pl $pku | |
# header: 08011240 | |
# ipfs key list -l --ipns-base base16 | grep self | |
# pub-self: f01721220d4ca21fd67b197375c10392f392adc4cd33fbce4575d435e23a664f0cbac60f7 | |
# ........ 1 2 3 4 5 6 |
*** Disclaimer this is a project in development ***
Not all features are readily available if you are a developper, a talented contributor, or a technology evengelist we will be delighted if you join us. if you want to fund the project to help its release, PLEASE do so
GIT already "cryptographically chain commits the only thing we are missing is a secure timestamp to have a concensus among the participants.
Using ots will provide timestamp on the bitcoin chain (BTC)
We only need a way to discover the HEAD (i.e. longuest chain) git pull $(pick-random-node)
# FRESH START !
unset NODE_ENV
sudo apt-get remove nodejs
sudo apt update
sudo apt autoremove
sudo apt upgrade
# problem with npm and node install
sudo apt-get install npm
apt-cache policy npm
#!/usr/bin/perl | |
# curl -I https://app.netlify.app/ | |
use YAML::XS qw(Dump); | |
my $resp = &head_url('http://clock.netlify.app/'); | |
#printf "resp: %s\n",Dump($resp); | |
#printf "headers: %s\n",Dump($resp->headers); | |
my $rid = $resp->headers()->{'x-nf-request-id'}; |
#define _GNU_SOURCE | |
#define _ATFILE_SOURCE | |
#include <stdio.h> | |
#include <stdlib.h> | |
#include <sys/types.h> | |
#include <unistd.h> | |
#include <fcntl.h> | |
#include "statx.h" | |
#include <time.h> | |
#include <getopt.h> |