LPX calls external, on-chain contracts for the following systems:
- Uniswap pair (add liq, remove liq)
- Uniswap price oracle, 30 minute interval. Ref: https://github.com/bloq/sol-price-oracles
- Whitelist. Ref: https://github.com/bloq/sol-address-list
LPX calls external, on-chain contracts for the following systems:
#include <stdio.h> | |
#include <stdexcept> | |
#include <unistd.h> | |
#include <fcntl.h> | |
#include <string> | |
#include <vector> | |
#include <string.h> | |
#include <assert.h> | |
#include <zlib.h> |
#include <stdio.h> | |
#include <unistd.h> | |
#include <fcntl.h> | |
#include <string> | |
#include <vector> | |
#include <assert.h> | |
#include <zlib.h> | |
using namespace std; |
#ifndef __SRV_BIDIPIPE_H__ | |
#define __SRV_BIDIPIPE_H__ | |
#include "Util.h" | |
#ifndef ARRAYLEN | |
#define ARRAYLEN(array) (sizeof(array)/sizeof((array)[0])) | |
#endif // ARRAYLEN | |
class BidiPipe { |
/* | |
Build: | |
g++ -std=c++11 -O -Wall -g -o eth-tx-prefix eth-tx-prefix.cc -lrocksdb | |
Run: | |
./eth-tx-prefix | |
Clean: |
diff --git a/configure.ac b/configure.ac | |
index a9156c3..50509d6 100644 | |
--- a/configure.ac | |
+++ b/configure.ac | |
@@ -1,6 +1,6 @@ | |
dnl require autoconf 2.60 (AS_ECHO/AS_ECHO_N) | |
AC_PREREQ([2.60]) | |
-define(_CLIENT_VERSION_MAJOR, 0) | |
+define(_CLIENT_VERSION_MAJOR, 1) | |
define(_CLIENT_VERSION_MINOR, 14) |
I hereby claim:
To claim this, I am signing this object:
Verifying that +jgarzik is my openname (Bitcoin username). https://onename.io/jgarzik |
#include <sys/types.h> | |
#include <sys/stat.h> | |
#include <stdio.h> | |
#include <stdlib.h> | |
#include <string.h> | |
#include <fcntl.h> | |
#include <time.h> | |
#include <stdint.h> | |
#include <stdbool.h> | |
#include <unistd.h> |
This protocol describes a simple payment channel protocol, such as the one presented in https://en.bitcoin.it/wiki/Contracts#Example_7:_Rapidly-adjusted_.28micro.29payments_to_a_pre-determined_party
JSON-RPC methods shown here may be sent via HTTPS or stratum protocol. It is easily adaptable to protocol buffers or another favored marshalling method.
Client requests a public key. Server responds with a public key (K2). K2, converted to a bitcoin address, forms the unique identifier for this payment channel. Each public key returned must be unique.