Payshares Ethereum Tokens are now trading versus WETH, DAI, and ZRX on BambooRelay : https://bamboorelay.com/trade/XPS-WETH
Be sure to use to the correct contract of 0x32EAB29Aa859e40365873c8a7562710E2250f640 https://etherscan.io/token/0x32eab29aa859e40365873c8a7562710e2250f640
Topic: [ANN][XPS] Payshares - Simplifying Money for Everyone (Read 5539 times)
Payshares Ethereum Tokens are now trading on LedgerDEX : https://ledgerdex.com
Be sure to use to the correct contract of 0x32EAB29Aa859e40365873c8a7562710E2250f640 https://etherscan.io/token/0x32eab29aa859e40365873c8a7562710e2250f640
In all there are 100,000,000,000 XPS at which half is to be distributed by various Airdrops. Recently, the Payshares Windows Client was published to https://github.com/Payshares/paysharesd/releases/download/0.28.0-k/paysharesd.exe and as such we are Airdropping 1,000,000,000 XPS to new users of the Payshares Platform. Simply Join us on Telegram with your Payshares Address generated by the Windows Client to participate.
Payshares for Windows is now available at Github: https://github.com/Payshares/paysharesd/releases/download/0.28.0-k/paysharesd.exe
With publication of this executable, five validators are being brought online with possible long term availability. The master validator remains at one.vld.payshares.org. Our secondary payshares.org validator is in a snapshot state to preserve integrity of the Payshares blockchain while recently discovered issues are resolved. This release is experimental with bounties for issue resolution ranging from 10,000 to 1,000,000 XPS. It is expected that unknown events related to paysharesd on Windows may occur. Post any discovered issues to https://github.com/Payshares/paysharesd/issues and solve the issue to receive an XPS Bounty.
RocksDB is currently not an option for storage on Windows. As such, daemon configuration and performance are different than linux flavors. In particular, users will notice that synching the Payshares Blockchain takes longer than usual to synchronize as SQLite is being used. Here is a sample paysharesd.cfg for Windows:
With publication of this executable, five validators are being brought online with possible long term availability. The master validator remains at one.vld.payshares.org. Our secondary payshares.org validator is in a snapshot state to preserve integrity of the Payshares blockchain while recently discovered issues are resolved. This release is experimental with bounties for issue resolution ranging from 10,000 to 1,000,000 XPS. It is expected that unknown events related to paysharesd on Windows may occur. Post any discovered issues to https://github.com/Payshares/paysharesd/issues and solve the issue to receive an XPS Bounty.
RocksDB is currently not an option for storage on Windows. As such, daemon configuration and performance are different than linux flavors. In particular, users will notice that synching the Payshares Blockchain takes longer than usual to synchronize as SQLite is being used. Here is a sample paysharesd.cfg for Windows:
Code:
# Allow other peers to connect to this server.
#
[network_quorum]
0
[peer_ip]
0.0.0.0
[peer_port]
52011
# Allow untrusted clients to connect to this server.
#
[websocket_public_ip]
0.0.0.0
[websocket_public_port]
5016
# Provide trusted websocket ADMIN access to the localhost.
#
[websocket_ip]
127.0.0.1
[websocket_port]
6016
# Provide trusted json-rpc ADMIN access to the localhost.
#
[rpc_ip]
127.0.0.1
[rpc_port]
5015
[rpc_allow_remote]
0
[node_size]
medium
# This is primary persistent datastore for paysharesd. This includes transaction
# metadata, account states, and ledger headers.
[node_db]
type=Sqlite
path=ledger.db
[database_path]
C:/payshares/payshares/conf/db
# This needs to be an absolute directory reference, not a relative one.
# Modify this value as required.
[debug_logfile]
C:/payshares/conf/debug.log
[sntp_servers]
time.windows.com
time.apple.com
time.nist.gov
pool.ntp.org
# Where to find some other servers speaking the Payshares protocol.
#
[ips]
one.vld.payshares.org 52011
two.vld.payshares.org 52011
[validators]
n3pYRu4G6iGZciPbSfD1WtK7XqZciLMTCzDCMufmaPUf49ta4z2 VLD1
nfp4HeeiLXt1NvJc7ZFYnUxCZFipwgNLAbZfMwpZhR6MdrvZbm1 VLD2
# Ditto.
[validation_quorum]
1
[consensus_threshold]
1
[ledger_history]
full
# Turn down default logging to save disk space in the long run.
# Valid values here are trace, debug, info, warning, error, and fatal
[rpc_startup]
{ "command": "log_level", "severity": "warning" }
# Configure SSL for WebSockets. Not enabled by default because not everybody
# has an SSL cert on their server, but if you uncomment the following lines and
# set the path to the SSL certificate and private key the WebSockets protocol
# will be protected by SSL/TLS.
#[websocket_secure]
#1
#[websocket_ssl_cert]
#/etc/ssl/certs/server.crt
#[websocket_ssl_key]
#/etc/ssl/private/server.key
# Defaults to 0 ("no") so that you can use self-signed SSL certificates for
# development, or internally.
#[ssl_verify]
#0
Reserved spanish translation for ANN+Bounty (if you have it) . Please confirm if you need it with a pm thanks. These are my previous works:
https://docs.google.com/spreadsheets/d/17GVSXk2YKqn5fCOnmW3DIynjKYhNq6g_jNMCeCEwvkI/edit?usp=sharing
https://docs.google.com/spreadsheets/d/17GVSXk2YKqn5fCOnmW3DIynjKYhNq6g_jNMCeCEwvkI/edit?usp=sharing
Payshares Client Version 0.12.1 has been released! The commit can be found on github at https://github.com/Payshares/payshares-client/commit/f97d1fed9237f7f4194be33323a6781d22715f10
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit f97d1fed9237f7f4194be33323a6781d22715f10
Author: Kedia <[email protected]>
Date: Tue Mar 20 16:10:12 2018 -0400
This is the Frost Cove Release and the first public distribution of the client. The Client functions across multiple platforms, however, support is initially being provided for Ubuntu. Although not a pre-release, this outcome is not considered production ready.
Improvements
=====================
* Updated js for live and test networks
* Added correct dependencies
* Completed XPS Conversion
* Improved Readme
* Added favicon
* Activated reCaptcha
* Passed subscribe option to email
* Updated to correct Payshares-lib
* Enhanced tooltip delay
* Started Two Factor Recovery
* Changed Minimum Balance
* Added new tests
* Improved SSL Coverage for websockets
* Separate API implementation
Assistance
------------
For assistance, please contact [email protected]
More information
-------------------
For more information or assistance, the following resources will be of use:
Payshares Website
Payshares Twitter
Payshares Facebook
Notes
-------
https://launch.payshares.org is ahead of the latest branch:
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit f97d1fed9237f7f4194be33323a6781d22715f10
Author: Kedia <[email protected]>
Date: Tue Mar 20 16:10:12 2018 -0400
This is the Frost Cove Release and the first public distribution of the client. The Client functions across multiple platforms, however, support is initially being provided for Ubuntu. Although not a pre-release, this outcome is not considered production ready.
Improvements
=====================
* Updated js for live and test networks
* Added correct dependencies
* Completed XPS Conversion
* Improved Readme
* Added favicon
* Activated reCaptcha
* Passed subscribe option to email
* Updated to correct Payshares-lib
* Enhanced tooltip delay
* Started Two Factor Recovery
* Changed Minimum Balance
* Added new tests
* Improved SSL Coverage for websockets
* Separate API implementation
Assistance
------------
For assistance, please contact [email protected]
More information
-------------------
For more information or assistance, the following resources will be of use:
Payshares Website
Payshares Twitter
Payshares Facebook
Notes
-------
https://launch.payshares.org is ahead of the latest branch:
Payshares Data API Version 0.4.1 has been released! The commit can be found on github at https://github.com/Payshares/payshares-data-api/commit/4166a48293a6001fa8392fbe30fb3fc53bf906d3
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 4166a48293a6001fa8392fbe30fb3fc53bf906d3
Author: Kedia <[email protected]>
Date: Tue Mar 20 15:10:55 2018 -0400
This is the Chai Tea Release and the first public distribution of the API. The API functions across multiple platforms, however, support is initially being provided for Ubuntu. Although not a pre-release, this outcome is not considered production ready.
Changes from the 0.0.1 Commit:
=====================
* Converted to unit code XPS
* Added correct dependencies
* Initialized Security Review Procedures
* Completed Tests for Paysharesd
* Set Ledger Start Time
* Cleaned up Documentation
* Output set to stdout
* Removed dead links
* Updated to latest Payshares-lib
* Fixed secure websocket
* Globally attach to Redis
* Enabled waiting for validated ledgers
* Started ledger hash validation
* Setup weekly historical data
* Put on new metrics data
Assistance
------------
For assistance, please contact [email protected]
More information
-------------------
For more information or assistance, the following resources will be of use:
Payshares Website
Payshares Twitter
Payshares Facebook
Notes
-------
Payshares API Live Ledger Import:
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 4166a48293a6001fa8392fbe30fb3fc53bf906d3
Author: Kedia <[email protected]>
Date: Tue Mar 20 15:10:55 2018 -0400
This is the Chai Tea Release and the first public distribution of the API. The API functions across multiple platforms, however, support is initially being provided for Ubuntu. Although not a pre-release, this outcome is not considered production ready.
Changes from the 0.0.1 Commit:
=====================
* Converted to unit code XPS
* Added correct dependencies
* Initialized Security Review Procedures
* Completed Tests for Paysharesd
* Set Ledger Start Time
* Cleaned up Documentation
* Output set to stdout
* Removed dead links
* Updated to latest Payshares-lib
* Fixed secure websocket
* Globally attach to Redis
* Enabled waiting for validated ledgers
* Started ledger hash validation
* Setup weekly historical data
* Put on new metrics data
Assistance
------------
For assistance, please contact [email protected]
More information
-------------------
For more information or assistance, the following resources will be of use:
Payshares Website
Payshares Twitter
Payshares Facebook
Notes
-------
Payshares API Live Ledger Import:
Payshares-lib 0.10.3 K has been released. The commit can be found on GitHub at: https://github.com/Payshares/payshares-lib/commit/abda6b2e6a478494c1674a0fac93be164a56bd33
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit abda6b2e6a478494c1674a0fac93be164a56bd33
Author: Kedia <[email protected]>
Date: Fri Mar 9 01:25:14 2018 -0500
This is the Salted Beef Release focused on Foundation Platforms. Short term support is being provided for Ubuntu 14.04 while interim support is being shifted to Ubuntu 16.04 scheduled for the summer of 2018.
0.7.35
LastLedgerSequence is set by default on outgoing transactions. This refers to the last valid ledger index (AKA sequence) for a transaction. By default, this index is set to the current index (at submission time) plus 8. In theory, this allows ripple-lib to deterministically fail a transaction whose submission request timed out, but whose associated server continues to emit ledger_closed events.
Transactions that err with telINSUF_FEE_P will be automatically resubmitted. This error indicates that the Fee supplied in the transaction submission request was inadquate. Ideally, the Fee is tracked by ripple-lib in real-time, and the resubmitted transaction will most likely succeed.
Added Transaction.iff(function(callback) { }). Callback expects first argument to be an Error or null, second argument is a boolean which indicates whether or not to proceed with the transaction submission. If an iff function is specified, it will be executed prior to every submission of the transaction (including resubmissions).
Transactions will now emit presubmit and postsubmit events. They will be emitted before and after a transaction is submitted, respectively.
Added Transaction.summary(). Returns a summary of a transaction in semi-human-readable form. JSON-stringifiable.
Remote.requestAccountTx() with binary: true will automatically parse transactions.
Added Remote.requestAccountTx filter, map, and reduce.
remote.requestAccountTx({
account: 'retc',
ledger_index_min: -1,
ledger_index_max: -1,
limit: 100,
binary: true,
filter: function(transaction) {
return transaction.tx.TransactionType === 'Payment';
},
map: function(transaction) {
return Number(transaction.tx.Amount);
},
reduce: function(a, b) {
return a + b;
},
pluck: 'transactions'
}, console.log)
Added persistence hooks.
General performance improvements, especially for long-running processes.
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit abda6b2e6a478494c1674a0fac93be164a56bd33
Author: Kedia <[email protected]>
Date: Fri Mar 9 01:25:14 2018 -0500
This is the Salted Beef Release focused on Foundation Platforms. Short term support is being provided for Ubuntu 14.04 while interim support is being shifted to Ubuntu 16.04 scheduled for the summer of 2018.
0.7.35
LastLedgerSequence is set by default on outgoing transactions. This refers to the last valid ledger index (AKA sequence) for a transaction. By default, this index is set to the current index (at submission time) plus 8. In theory, this allows ripple-lib to deterministically fail a transaction whose submission request timed out, but whose associated server continues to emit ledger_closed events.
Transactions that err with telINSUF_FEE_P will be automatically resubmitted. This error indicates that the Fee supplied in the transaction submission request was inadquate. Ideally, the Fee is tracked by ripple-lib in real-time, and the resubmitted transaction will most likely succeed.
Added Transaction.iff(function(callback) { }). Callback expects first argument to be an Error or null, second argument is a boolean which indicates whether or not to proceed with the transaction submission. If an iff function is specified, it will be executed prior to every submission of the transaction (including resubmissions).
Transactions will now emit presubmit and postsubmit events. They will be emitted before and after a transaction is submitted, respectively.
Added Transaction.summary(). Returns a summary of a transaction in semi-human-readable form. JSON-stringifiable.
Remote.requestAccountTx() with binary: true will automatically parse transactions.
Added Remote.requestAccountTx filter, map, and reduce.
remote.requestAccountTx({
account: 'retc',
ledger_index_min: -1,
ledger_index_max: -1,
limit: 100,
binary: true,
filter: function(transaction) {
return transaction.tx.TransactionType === 'Payment';
},
map: function(transaction) {
return Number(transaction.tx.Amount);
},
reduce: function(a, b) {
return a + b;
},
pluck: 'transactions'
}, console.log)
Added persistence hooks.
General performance improvements, especially for long-running processes.
Paysharesd 0.28.0 K has been released. The commit can be found on GitHub at: https://github.com/payshares/paysharesd/commit/addbc68a7ca6d11f6b6891fdae37198a6d78b11f
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit addbc68a7ca6d11f6b6891fdae37198a6d78b11f
Author: Kedia <[email protected]>
Date: Fri Mar 9 00:05:03 2018 -0500
This is the Latest Stable Release focused on Foundation Platforms. Short term support is being provided for Ubuntu 14.04 while interim support is being shifted to Ubuntu 16.04 scheduled for the summer of 2018.
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit addbc68a7ca6d11f6b6891fdae37198a6d78b11f
Author: Kedia <[email protected]>
Date: Fri Mar 9 00:05:03 2018 -0500
This is the Latest Stable Release focused on Foundation Platforms. Short term support is being provided for Ubuntu 14.04 while interim support is being shifted to Ubuntu 16.04 scheduled for the summer of 2018.
The Official Payshares Wiki is available at https://github.com/Payshares/wiki and contains the latest build instructions for the platform. The top level validator is now located at one.vld.payshares.org and is present for public use.
what get usual user ?
The Payshares Team has issued its first Bounty: https://payshares.co/blog/2015/06/11/design-bounty.html
That is so many Payshares are you joke 1m for design ?
what price your goal if Payshares listed on market ?
Well, your config files are broken, so I can't verify if you are vulnerable as it is impossible to connect to your network - also you don't seem to actually do anything on that ledger (your total_coins number hasn't changed). Do you offer bug bounties?
This seems to be a fork of Stellar which is a (back then already slightly stale) fork of Ripple. Any plans to update with more recent improvements from upstream rippled, as stellard is being rewritten significantly after all?
Also it is not unlikely that you are also vulnerable to some issues that Ripple recently fixed.
Also it is not unlikely that you are also vulnerable to some issues that Ripple recently fixed.
any news?
How should distribution of the Payshares Supply occur? embed
1. Perform a Giveaway
3 votes (60%)
2. Host an ICO
1 vote (20%)
3. Let developers retain it
1 vote (20%)
5 total votes
Only 5 people vote on https://strawpoll.me/4354114/r
I am waiting for news are this coin will be launch or not,,,?
1. Perform a Giveaway
3 votes (60%)
2. Host an ICO
1 vote (20%)
3. Let developers retain it
1 vote (20%)
5 total votes
Only 5 people vote on https://strawpoll.me/4354114/r
I am waiting for news are this coin will be launch or not,,,?
exchange is offline..
https://treefunder.co/
and market page does not exist
https://treefunder.co/markets/xltbtc
https://treefunder.co/
and market page does not exist
https://treefunder.co/markets/xltbtc
Would have been a little bit interesting seeing a snapshot ripple/stellar clone. Those always make everyone so upset.
exchange is offline..
https://treefunder.co/
and market page does not exist
https://treefunder.co/markets/xltbtc
https://treefunder.co/
and market page does not exist
https://treefunder.co/markets/xltbtc
So how to be distributed?
Any updates?
Look good 
Never saw ripple clone before.
Let see....
Never saw ripple clone before.
Let see....
One Step Closer
are this stellar clone
well well well
this coin will be share like stellar give away? true or wrong
Of course there are fair distribution plans for the Payshares Platform
Why this and not ripple? or stellar?
Waste of time i think
Waste of time i think
One Step Closer
are this stellar clone
well well well
this coin will be share like stellar give away? true or wrong
One Step Closer
My question:
...
...
The supply isn't mineable and reads as 99,999,999,999.999000 XPR at 1% inflation. 100 Billion Units is hardly ridiculous and participants may obtain units through participation on Twitter and Facebook.
Maybe I'm being critical. I just don't see any innovation or reason for this coin to exist though. :/
My question:
Is this some sort of premined piece of shit coin like ripple?
Not much for info on this launch and it smells pretty rippley.. that isn't a good thing.
*edit: Total coins: 99999999999999000... Only a fucking FOOL would get involved with a project with a ridiculous amount such as this.
Is this some sort of premined piece of shit coin like ripple?
Not much for info on this launch and it smells pretty rippley.. that isn't a good thing.
*edit: Total coins: 99999999999999000... Only a fucking FOOL would get involved with a project with a ridiculous amount such as this.
Development Update:
Payshares is now forging consensus and the initial reference implementation of XPR is available at https://github.com/payshares/paysharesd
Support is being provided for Ubuntu 14.04 LTS 64-bit. It is recommended to have at least 2 GB RAM, a quad core processor, and adequate disk space. Installation of paysharesd on Ubuntu 14.04 is relatively straightforward with administrator privileges:
Code:
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install git autoconf autogen automake build-essential software-properties-common libboost-all-dev libcurl4-openssl-dev libdb-dev libdb++-dev libgmp3-dev libminiupnpc-dev libmpfr-dev libssl-dev libcurl4-openssl-dev libjansson-dev pax-utils
sudo apt-get install git scons ctags pkg-config protobuf-compiler libprotobuf-dev libssl-dev python-software-properties libboost1.55-all-dev g++ make
sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.8 40 --slave /usr/bin/g++ g++ /usr/bin/g++-4.8
sudo update-alternatives --config gcc
wget https://download.libsodium.org/libsodium/releases/LATEST.tar.gz
tar xzf LATEST.tar.gz
cd libsodium-*/
./configure
make && make check && sudo make install
cd ..
git clone https://github.com/payshares/paysharesd.git
cd paysharesd/
scons
sudo apt-get upgrade
sudo apt-get install git autoconf autogen automake build-essential software-properties-common libboost-all-dev libcurl4-openssl-dev libdb-dev libdb++-dev libgmp3-dev libminiupnpc-dev libmpfr-dev libssl-dev libcurl4-openssl-dev libjansson-dev pax-utils
sudo apt-get install git scons ctags pkg-config protobuf-compiler libprotobuf-dev libssl-dev python-software-properties libboost1.55-all-dev g++ make
sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.8 40 --slave /usr/bin/g++ g++ /usr/bin/g++-4.8
sudo update-alternatives --config gcc
wget https://download.libsodium.org/libsodium/releases/LATEST.tar.gz
tar xzf LATEST.tar.gz
cd libsodium-*/
./configure
make && make check && sudo make install
cd ..
git clone https://github.com/payshares/paysharesd.git
cd paysharesd/
scons
After compilation, paysharesd will be available within the 'build' directory. paysharesd.cfg should be placed in the ~/.config/payshares directory. Create the following directories:
Code:
(if not exists):
mkdir ~/.config
mkdir ~/.config/payshares
mkdir ~/.config/payshares/db
mkdir ~/.config
mkdir ~/.config/payshares
mkdir ~/.config/payshares/db
The published documentation will be updated to reflect the initial validating node as referenced in the following example paysharesd.cfg:
Code:
# Allow other peers to connect to this server.
#
[peer_ip]
0.0.0.0
[peer_port]
52011
# Allow untrusted clients to connect to this server.
#
[websocket_public_ip]
0.0.0.0
[websocket_public_port]
5016
# Provide trusted websocket ADMIN access to the localhost.
#
[websocket_ip]
127.0.0.1
[websocket_port]
6016
# Provide trusted json-rpc ADMIN access to the localhost.
#
[rpc_ip]
127.0.0.1
[rpc_port]
5015
[rpc_allow_remote]
0
[node_size]
medium
# This is primary persistent datastore for paysharesd. This includes transaction
# metadata, account states, and ledger headers.
[node_db]
type=RocksDB
path=/.config/payshares/db/rocksdb
open_files=2000
filter_bits=12
cache_mb=256
file_size_mb=8
file_size_mult=2
[database_path]
/.config/payshares/db
# This needs to be an absolute directory reference, not a relative one.
# Modify this value as required.
[debug_logfile]
/.config/payshares/debug.log
[sntp_servers]
time.windows.com
time.apple.com
time.nist.gov
pool.ntp.org
# Where to find some other servers speaking the Payshares protocol.
#
[ips]
validator.payshares.co 52011
[validators]
naLkDUxjwnGDfwgRW82MtzzctajnJq8YKsdmMXRTus8FRvZ3ABr VLD0
# Ditto.
[validation_quorum]
1
[consensus_threshold]
1
# Turn down default logging to save disk space in the long run.
# Valid values here are trace, debug, info, warning, error, and fatal
[rpc_startup]
{ "command": "log_level", "severity": "warning" }
# Configure SSL for WebSockets. Not enabled by default because not everybody
# has an SSL cert on their server, but if you uncomment the following lines and
# set the path to the SSL certificate and private key the WebSockets protocol
# will be protected by SSL/TLS.
#[websocket_secure]
#1
#[websocket_ssl_cert]
#/etc/ssl/certs/server.crt
#[websocket_ssl_key]
#/etc/ssl/private/server.key
# Defaults to 0 ("no") so that you can use self-signed SSL certificates for
# development, or internally.
#[ssl_verify]
#0
#
[peer_ip]
0.0.0.0
[peer_port]
52011
# Allow untrusted clients to connect to this server.
#
[websocket_public_ip]
0.0.0.0
[websocket_public_port]
5016
# Provide trusted websocket ADMIN access to the localhost.
#
[websocket_ip]
127.0.0.1
[websocket_port]
6016
# Provide trusted json-rpc ADMIN access to the localhost.
#
[rpc_ip]
127.0.0.1
[rpc_port]
5015
[rpc_allow_remote]
0
[node_size]
medium
# This is primary persistent datastore for paysharesd. This includes transaction
# metadata, account states, and ledger headers.
[node_db]
type=RocksDB
path=
open_files=2000
filter_bits=12
cache_mb=256
file_size_mb=8
file_size_mult=2
[database_path]
# This needs to be an absolute directory reference, not a relative one.
# Modify this value as required.
[debug_logfile]
[sntp_servers]
time.windows.com
time.apple.com
time.nist.gov
pool.ntp.org
# Where to find some other servers speaking the Payshares protocol.
#
[ips]
validator.payshares.co 52011
[validators]
naLkDUxjwnGDfwgRW82MtzzctajnJq8YKsdmMXRTus8FRvZ3ABr VLD0
# Ditto.
[validation_quorum]
1
[consensus_threshold]
1
# Turn down default logging to save disk space in the long run.
# Valid values here are trace, debug, info, warning, error, and fatal
[rpc_startup]
{ "command": "log_level", "severity": "warning" }
# Configure SSL for WebSockets. Not enabled by default because not everybody
# has an SSL cert on their server, but if you uncomment the following lines and
# set the path to the SSL certificate and private key the WebSockets protocol
# will be protected by SSL/TLS.
#[websocket_secure]
#1
#[websocket_ssl_cert]
#/etc/ssl/certs/server.crt
#[websocket_ssl_key]
#/etc/ssl/private/server.key
# Defaults to 0 ("no") so that you can use self-signed SSL certificates for
# development, or internally.
#[ssl_verify]
#0
seems like czarparty
web is not available LOL
Payshares is an open source protocol for exchange, payments, and remittance forged by Kedia. Its base components include an open distributed ledger system and native currency payshare units known as XPS. The Payshares Platform enhances the cryptocurrency industry with near instant extremely low cost transactions with great risk reduction for all participants.
Website : https://payshares.org
Github : https://github.com/payshares
Payshares for Windows: https://github.com/Payshares/paysharesd/releases/download/0.28.0-k/paysharesd.exe
Documentation : https://github.com/payshares/docs
Wallet: https://launch.payshares.org
Initial Supply : 100,000,000,000 XPS at 1% inflation.
The Payshares Ledger holds all account information, transactions, and offers available on the network. Participants on the network are able to reach consensus in average of one to five seconds. Consensus allows for the network to operate in a distributed fashion.
Everyone is able to participate and contribute computational power to the network on standard hardware. Standard Servers reduce storage requirements by maintaining a recent snapshot of the ledger. Trusted Nodes such as those in operation by Kedia will maintain the full ledger.
Every feature currently available in its competitors is also currently available for Payshares. Unique to Payshares is the expansion capabilities of its distributed exchange, opening up asset management opportunities previously only achievable by centralized financial systems.
Social Media
Telegram Channel
Telegram Group
Payshares Genesis Ledger:
Code:
{
"result" : {
"ledger" : {
"accepted" : true,
"account_hash" : "CD61677B53191E1FDCA8861E68B11688B86260A5DE55429942FB79EE3D066BCF",
"close_time" : 559688910,
"close_time_human" : "2017-Sep-25 21:08:30",
"close_time_resolution" : 30,
"closed" : true,
"fee_pool" : "0",
"hash" : "F5524981DB75D730771449FAEF7ED46F621193638F96B2DDAFF456B7925EE46A",
"inflate_seq" : "1",
"ledger_hash" : "F5524981DB75D730771449FAEF7ED46F621193638F96B2DDAFF456B7925EE46A",
"ledger_index" : "1",
"parent_hash" : "0000000000000000000000000000000000000000000000000000000000000000",
"seqNum" : "1",
"totalCoins" : "100000000000000000",
"total_coins" : "100000000000000000",
"transaction_hash" : "0000000000000000000000000000000000000000000000000000000000000000"
},
"status" : "success"
}
}
"result" : {
"ledger" : {
"accepted" : true,
"account_hash" : "CD61677B53191E1FDCA8861E68B11688B86260A5DE55429942FB79EE3D066BCF",
"close_time" : 559688910,
"close_time_human" : "2017-Sep-25 21:08:30",
"close_time_resolution" : 30,
"closed" : true,
"fee_pool" : "0",
"hash" : "F5524981DB75D730771449FAEF7ED46F621193638F96B2DDAFF456B7925EE46A",
"inflate_seq" : "1",
"ledger_hash" : "F5524981DB75D730771449FAEF7ED46F621193638F96B2DDAFF456B7925EE46A",
"ledger_index" : "1",
"parent_hash" : "0000000000000000000000000000000000000000000000000000000000000000",
"seqNum" : "1",
"totalCoins" : "100000000000000000",
"total_coins" : "100000000000000000",
"transaction_hash" : "0000000000000000000000000000000000000000000000000000000000000000"
},
"status" : "success"
}
}
Jump to: