plowsof

Install i2pd debian/ubuntu:

sudo add-apt-repository ppa:purplei2p/i2pd
sudo apt-get update
sudo apt-get install i2pd

stop i2pzero service

Initial feedback received from CypherStack for the latest blockstream BP++ paper:

There are several aspects of the preprint that should be considered out of scope for a review:

Multiparty computation. There are no specific protocols presented for this, and no corresponding security model of proofs of security.
Batch verification. While the preprint mentions that BP++ supports batch verification, it provides no details on the corresponding algebra.
Multi-asset transactions. The preprint discusses multi-asset transactions in the context of its protocols, but these are not required for range proofs.
Optimized binary range proofs. The protocol proposed for optimized binary range proofs has only an informal and vague security proof that is insufficient to assert the claims of the corresponding theorem.

Jberman / Kayaba / Koe have helped created a rough scope of initial work for the Seraphis papers which can be seen below.

Read through the Seraphis papers (the paper describing the transaction protocol and its companion paper spec'ing its implementation)
- Link to Seraphis papers: https://github.com/UkoeHB/Seraphis/tree/master
Establish a formal security model to prove Seraphis secure under.
- Section 1.2 in the Seraphis paper sketches a model but is light on details. Plausible path: rework section 1.2 such that it can be formalized in terms of algorithms and/or experiments.
Formalize the respective algorithms in the instantiation of Seraphis and see if the Seraphis construction is amenable to proofs under the chosen security model.
- If the Seraphis construction is not amenable to a chosen security model, then it would still be useful to formalize security proofs for individual components of Seraphis (membership, ownership, unspentness, amounts balance).
One researcher we've contacted sugges

	-----BEGIN PGP SIGNED MESSAGE-----
	Hash: SHA256

	i run these nodes. they suffer from connctivity issues sadly.

	plowsof3t5hogddwabaeiyrno25efmzfxyro2vligremt7sxpsclfaid.onion
	plowsoffjexmxalw73tkjmf422gq6575fc7vicuu4javzn2ynnte6tyd.onion
	plowsofe6cleftfmk2raiw5h2x66atrik3nja4bfd3zrfa2hdlgworad.onion

	=== monero info ===

	import asyncio
	import logging
	from nio import (
	AsyncClient, RoomMessageText, RoomCreateResponse, RoomCreateError,
	LoginResponse, RoomPreset, RoomVisibility
	)
	import aiosqlite
	from datetime import datetime

	# Set up logging

	from monerorpc.authproxy import AuthServiceProxy, JSONRPCException
	import os, requests, time
	#./monero-wallet-rpc --disable-rpc-login --rpc-bind-port 18082 --stagenet --wallet-dir /home/human/monero/build/Linux/view_sync/release/bin --daemon-host node2.monerodevs.org:38089 --trusted --no-initial-sync
	wallet_dir = "/home/human/monero/build/Linux/view_sync/release/bin"
	daemon_address = "node2.monerodevs.org:38089"
	rpc_url = "http://127.0.0.1:18082/json_rpc"
	test_wallet = "stager"
	rpc_connection = AuthServiceProxy(service_url=rpc_url)
	original_balance = 0

	from monerorpc.authproxy import AuthServiceProxy, JSONRPCException
	import os
	#./monero-wallet-rpc --disable-rpc-login --rpc-bind-port 18082 --stagenet --wallet-dir /home/human/monero/build/Linux/view_sync/release/bin --daemon-host node2.monerodevs.org:38089 --trusted
	wallet_dir = "/home/human/monero/build/Linux/view_sync/release/bin"
	daemon_address = "node2.monerodevs.org:38089"
	rpc_url = "http://127.0.0.1:18082/json_rpc"
	test_wallet = "stager"
	rpc_connection = AuthServiceProxy(service_url=rpc_url)
	original_balance = 0