Angel Leon gubatron

A pseudonymous trust system for a decentralized anonymous marketplace

Dionysis Zindros, National Technical University of Athens [email protected]

Keywords

pseudonymous anonymous web-of-trust identity trust bitcoin namecoin proof-of-burn timelock decentralized anonymous marketplace openbazaar

Abstract

DHT Walkthrough Notes

I've put together these notes as I read about DHT's in depth and then learned how the libtorrent implementation based on the Kademlia paper actually works.

What problem does this solve?

400,000,000,000 (400 billion stars), that's a 4 followed by 11 zeros. The number of atoms in the universe is estimated to be around 10^82. A DHT with keys of 160 bits, can have 2^160 possible numbers, which is around 10^48

Things to remember when compiling/linking C/C++ software

by Angel Leon. March 17, 2015;

Last update on December 14, 2023

Updated on February 27, 2023

Updated August 29, 2019.

GPG gives a lot of shit on macos for some reason.

It's best to just add the same SSH authentication key you have on github as a "Signing Key"

$ git config [--global] gpg.format ssh
$ git config [--global] user.signingkey ~/.ssh/id_rsa.pub
$ git config [--global] commit.gpgsign true

	require 'rubygems'
	require 'mechanize'

	FIRST_NAME = 'FIRST_NAME'
	LAST_NAME = 'LAST_NAME'
	PHONE = 'PHONE'
	EMAIL = '[email protected]'

	PARTY_SIZE = 2
	SCHEDULE_RANGE = { :start_time => '19:00', :end_time => '20:30' }

	'''
	INITIAL IDEA:
	Just to illustrate idea on how I believe the maximum block size should be determined.

	My idea stems from a simple scalability metric that affects real users and the desire to use Bitcoin:
	Waiting times to get your transactions confirmed on the blockchain.
	Anything past 45mins-1 hour should be unnacceptable.

	Initially I wanted to measure the mean time for the transactions in blocks to go from being sent by the user
	(initial broadcast into mempools) until the transaction was effectively