Topic: [ANN][XPS] Payshares - Simplifying Money for Everyone (Read 5525 times)

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

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:

Distribution Goals posted to https://payshares.org

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

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:

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:

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.

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.

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 ?

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.

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,,,?

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

 

So how to be distributed?