[PASC] PascalCoin: Induplicatable NFT

[tlaskows]

Hi Thomas. What's good? My wife would say I'm only about 20% human.

That's 18% more than me.

My wife.  She doesn't exist.  She was boring.

I don't have one.

But I've heard than I'm non compliant 9000 times.

[1715190112]

1715190112

[1715190112]

1715190112

[1715190112]

1715190112

[PascalCoin]

Dear PascalCoin users,

New PascalCoin Build 3.0.0

Available source code at Github (Release 3.0.0), also available compiled binaries at Sourceforge (Windows installer / Linux binaries)

Windows installer/Binaries at Sourceforge: https://sourceforge.net/projects/pascalcoin/files
Release at Github: https://github.com/PascalCoin/PascalCoin/releases/tag/3.0.0

### Build 3.0.0 - 2018-05-02
- Implementation of Hard fork on block 210000
  - PIP - 0010: 50% inflation reduction
  - PIP - 0011: 20% Development reward
  - PIP - 0017: Anonymity via transaction mixing (multioperation)
  - New target calc on protocol V3 in order to reduce the sinusoidal effect
    - Harmonization of the sinusoidal effect modifying the rise / fall by 50% calculating over the last 10 blocks only when increase/decrease is high
- New Safebox Snapshoting
  - This allow quickly rollback/commit directly to Safebox instead of create a separate Safebox on memory (read from disk... use more ram...)
  - Is usefull when detecting posible orphan blocks in order to check which chain is the highest chain without duplicating a safebox to compare
- New Node network operations
  - Get pending operations (code $0030)
    - Implementation of the PIP-0013 (not exactly but with similar features)   
  - Get account (code $0031)
    - This call will allow a simple third party app communicate directly to a node to get account info (balance, n_operation, name, public key... )
  - Reserverd codes from $1000 to $1FFF
    - A node will not break connection if those codes are used, but will response with ERRORCODE_NOT_IMPLEMENTED ($00FF)
- MultiOperation: PIP-0017
  - Multioperation allows a transactional like operations, they can include transactions and change info operations in a signle multioperation
    - Allow to send coins from N accounts to M receivers in a transaction mixing, without knowledge of how many coins where sent from "Alice" to "Bob" if properly mixed
   - Ophash can be previously known by all signers before signing. They must sign only if multioperation includes it's transactions as expected
   - OpHash of a multioperation will allow to include n_operation and account of each signer account, but md160hash chunk will be the same for all
- JSON-RPC changes:
  - Added param "startblock" to "getaccountoperations" in order to start searching backwards on a specific block. Note: Balance will not be returned on each operation due cannot be calculated. Default value "0" means start searching on current block as usual
  - Operation Object changes:
    New fields:
    - "senders" : ARRAY of objects - When is a transaction, this array contains each sender
      - "account" : Sending Account
      - "n_operation"
      - "amount" : PASCURRENCY - In negative value, due it's outgoing from "account"
      - "payload" : HEXASTRING
    - "receivers" : ARRAY of objects - When is a transaction, this array contains each receiver
      - "account" : Receiving Account
      - "amount" : PASCURRENCY - In positive value, due it's incoming from a sender to "account"
      - "payload" : HEXASTRING
    - "changers" : ARRAY of objects - When accounts changed state
      - "account" : changing Account
      - "n_operation"
      - "new_enc_pubkey" : If public key is changed or when is listed for a private sale
      - "new_name" : If name is changed
      - "new_type" : If type is changed
      - "seller_account" : If is listed for sale (public or private) will show seller account
      - "account_price"   : PASCURRENCY - If is listed for sale (public or private) will show account price
      - "locked_until_block" : If is listed for private sale will show block locked
      - "fee" : PASCURRENCY - In negative value, due it's outgoing from "account"
    Modified fields / DEPRECATED FIELDS
    Caused by multioperation introduction, search in "senders"/"receivers"/"changers" instead
    - "balance" will not be included when is not possible to calc previous balance of account searching at the past
    - "signer_account" will not be included in Multioperations
    - "account" : will not be included in Multioperations, use fields in "senders"/"receivers"/"changers" instead   
    - "n_operation" will not be included in Multioperations, use fields in "senders"/"receivers"/"changers" instead
    - "payload" will not be included in Multioperations, use fields in "senders"/"receivers"/"changers" instead
    - "sender_account" is not correct to be used. Use "account" param on "senders" array instead
    - "dest_account" is not correct to be used. Use "account" param on "receivers" array instead
    - "amount" is not correct to be used. Use each "amount" param on "senders/receivers" instad. Note: sender "amount" is a negative number, positive for receiver
  - New object "MultiOperation Object" : Will return info about a MultiOperation
    - "rawoperations" : HEXASTRING with this single MultiOperation in RAW format
    - "senders" : Will return an Array with Objects
      - "account" : Sending Account
      - "n_operation"
      - "amount" : In negative value, due it's outgoing from "account"
      - "payload"
    - "receivers"
      - "account" : Receiving Account
      - "amount" : In positive value, due it's incoming from a sender to "account"
      - "payload"
    - "changers" : Will return an Array with Objects
      - "account" : changing Account
      - "n_operation"
      - "new_enc_pubkey" : If public key is changed
      - "new_name" : If name is changed
      - "new_type" : If type is changed
    - "amount" : PASCURRENCY Amount received by receivers
    - "fee" : PASCURRENCY Equal to "total send" - "total received"
   - "signed_count" : Integer with info about how many accounts are signed. Does not check if signature is valid for a multioperation not included in blockchain
   - "not_signed_count" : Integer with info about how many accounts are pending to be signed
    - "signed_can_execute"   : Boolean. True if everybody signed. Does not check if MultiOperation is well formed or can be added to Network because is an offline call
  - New method "signmessage": Signs a digest message using a public key
    - Params:
      - "digest" : HEXASTRING with the message to sign
     - "b58_pubkey" or "enc_pubkey" : HEXASTRING with the public key that will use to sign "digest" data
    - Result: False on error
      - "digest" : HEXASTRING with the message to sign
     - "enc_pubkey" : HESATRING with the public key that used to sign "digest" data
     - "signature" : HEXASTRING with signature
  - New method "verifysign": Verify if a digest message is signed by a public key
    - Params:
      - "digest" : HEXASTRING with the message to check
     - "b58_pubkey" or "enc_pubkey" : HEXASTRING with the public key that used to sign "digest" data
     - "signature" : HEXASTRING returned by "signmessage" call
    - Result: False on error
      - "digest" : HEXASTRING with the message to check
     - "enc_pubkey" : HESATRING with the public key that used to sign "digest" data
     - "signature" : HEXASTRING with signature
  - New method "multioperationaddoperation": Adds operations to a multioperation (or creates a new multioperation and adds new operations)
    This method does not need current Safebox state, so can be used offline or on COLD wallets when all info is provided
    - Params:
      - "rawoperations" : HEXASTRING (optional) with previous multioperation. If is valid and contains a single  multiopertion will add operations to this one, otherwise will generate a NEW MULTIOPERATION
     - "auto_n_operation" : Boolean - Will fill n_operation (if not provided). Only valid if wallet is ONLINE (no cold wallets)
      - "senders" : ARRAY of objects that will be Senders of the multioperation
        - "account" : Integer
        - "n_operation" : Integer (optional) - if not provided, will use current safebox n_operation+1 value (on online wallets)
        - "amount" : PASCURRENCY in positive format
        - "payload" : HEXASTRING
      - "receivers" : ARRAY of objects that will be Receivers of the multioperation
        - "account" : Integer
        - "amount" : PASCURRENCY in positive format
        - "payload" : HEXASTRING
      - "changesinfo" : ARRAY of objects that will be accounts executing a changing info
        - "account" : Integer
        - "n_operation" : Integer (optional) - if not provided, will use current safebox n_operation+1 value (on online wallets)
        - "new_b58_pubkey"/"new_enc_pubkey": (optional) If provided will update Public key of "account"
        - "new_name" : STRING (optional) If provided will change account name
        - "new_type" : Integer (optional) If provided will change account type
    - Result:
      If success will return a "MultiOperation Object"
  - New method "multioperationsignoffline"
    This method will sign a Multioperation found in a "rawoperations"
   Must provide info about accounts and keys (current Safebox state, provided by an ONLINE wallet)
    - Params:
      -   "rawoperations" : HEXASTRING with 1 multioperation in Raw format
      - "accounts_and_keys"   : ARRAY of objects with info about accounts and public keys to sign
        - "account" : Integer
        - "b58_pubkey" or "enc_pubkey" : HEXASTRING with the public key of the account
    - Result:
      If success will return a "MultiOperation Object"
  - New method "multioperationsignonline"
    This method will sign a Multioperation found in a "rawoperations" based on current safebox state public keys
   Must provide info about accounts and keys (current Safebox state, provided by an ONLINE wallet)
    - Params:
      -   "rawoperations" : HEXASTRING with 1 multioperation in Raw format
    - Result:
      If success will return a "MultiOperation Object"
  - New method "operationsdelete"
    This method will delete an operation included in a Raw operations object
    - Params:
      -   "rawoperations" : HEXASTRING with Raw Operations Object
    - Result:
      If success will return a "Raw Operations Object"
      - "rawoperations" : HEXASTRING with operations in Raw format
      - "operations" : Integer
      - "amount" : PASCURRENCY
      - "fee" : PASCURRENCY 
  - Updated method "getpendings" : Added params "start" (0..N) default=0 and "max" default=100 (0 = ALL)
    - Also fixed bug #86 : https://github.com/PascalCoin/PascalCoin/issues/86
  - New method "getpendingscount" : Returns pending operations count
- Daemon:
  - Allow to force max block read from Blockchain when started using "-b MAX_BLOCK_NUMBER" param. Example "nohup ./pascalcoin_daemon -r -b 12345 &"
- Protections against invalid nodes (scammers):
  - Protection on GetBlocks and GetBlockOperations
- Merged new GUI with current stable core
- New folders organization
- Bugs solved

This is a HARD FORK release, upgrade is mandatory

Go go go $PASC !!!

[Blocktree]

What about changing to a more POP name,not a coding name?

[caffeman]

What about changing to a more POP name,not a coding name?

yeah,PascalCoin need a new brand,new name,shorter and closer.

[tlaskows]

What about changing to a more POP name,not a coding name?

POP name?

Pascal was a French mathematician, philosopher, physicist...

They didn't have computers in 1600s.

Pascal, Delphi.   Those languages were named for a reason.

An oracle in ancient Greece could see the future.

Feels like nothing has changed.

[Skybuck]

Dear PascalCoin users,

New PascalCoin Build 3.0.0

### Build 3.0.0 - 2018-05-02
- Implementation of Hard fork on block 210000
  - PIP - 0017: Anonymity via transaction mixing (multioperation)
- MultiOperation: PIP-0017
  - Multioperation allows a transactional like operations, they can include transactions and change info operations in a signle multioperation
    - Allow to send coins from N accounts to M receivers in a transaction mixing, without knowledge of how many coins where sent from "Alice" to "Bob" if properly mixed
   - Ophash can be previously known by all signers before signing. They must sign only if multioperation includes it's transactions as expected
   - OpHash of a multioperation will allow to include n_operation and account of each signer account, but md160hash chunk will be the same for all

Have to comment on this "mixing".

People are not to trust this too much.

This paper is a nice read for those experimenting with coin mixing:

"When the cookie meets the blockchain" !

https://arxiv.org/pdf/1708.04748.pdf

It's been mentioned on slashdot.org

https://yro.slashdot.org/story/17/08/21/2038239/third-party-trackers-on-web-shops-can-identify-users-behind-bitcoin-transactions

A disturbing quote from the paper's introduction:

"
Our second attack shows that
if the tracker is able to link two purchases of the same user to the
blockchain in this manner, it can identify the user’s entire cluster
of addresses and transactions on the blockchain, even if the user
employs blockchain anonymity techniques such as CoinJoin. The
attacks are passive and hence can be retroactively applied to past
purchases.  We  discuss  several  mitigations,  but  none  are  perfect
"

CoinJoin is a bitcoin mixer.

https://en.bitcoin.it/wiki/CoinJoin

So I am very doubtfull how usefull this new pascalcoin feature will be for protecting privacy

[lieutkcb]

Can I join in now? How can I participate in ?

[PascalCoin]

Dear PascalCoin users,

New PascalCoin Build 3.0.1

Build 3.0.1 - 2018-05-07
- Deprecated use of OpenSSL v1.0 versions. Only allowed OpenSSL v1.1 versions
- JSON-RPC Added param "openssl" on "nodestatus" call. Will return OpenSSL library version as described in OpenSSL_version_num ( https://www.openssl.org/docs/man1.1.0/crypto/OPENSSL_VERSION_NUMBER.html )

Please note:
- Linux users: Old versions of PascalCoin are (by default) running OpenSSL v1.1, you don't need to upgrade if you're using last release build 3.0.
- Windows users: By default PascalCoin was using OpenSSL v1.0, currently deprecated, this is mandatory to UPGRADE in order to use OpenSSL v1.1

You will find source code on Github:
https://github.com/PascalCoin/PascalCoin/releases/tag/3.0.1

Binaries also at Github or at SourceForge:
https://sourceforge.net/projects/pascalcoin

Remember: Hard fork activation at block 210000, probably on Thursday, 31-May-18
Mandatory upgrade to Version 3 prior to block 210000

[tlaskows]

Dear PascalCoin users,

New PascalCoin Build 3.0.1

Build 3.0.1 - 2018-05-07
- Deprecated use of OpenSSL v1.0 versions. Only allowed OpenSSL v1.1 versions
- JSON-RPC Added param "openssl" on "nodestatus" call. Will return OpenSSL library version as described in OpenSSL_version_num ( https://www.openssl.org/docs/man1.1.0/crypto/OPENSSL_VERSION_NUMBER.html )

Please note:
- Linux users: Old versions of PascalCoin are (by default) running OpenSSL v1.1, you don't need to upgrade if you're using last release build 3.0.
- Windows users: By default PascalCoin was using OpenSSL v1.0, currently deprecated, this is mandatory to UPGRADE in order to use OpenSSL v1.1

You will find source code on Github:
https://github.com/PascalCoin/PascalCoin/releases/tag/3.0.1

Binaries also at Github or at SourceForge:
https://sourceforge.net/projects/pascalcoin

Remember: Hard fork activation at block 210000, probably on Thursday, 31-May-18
Mandatory upgrade to Version 3 prior to block 210000

Thank you for the update.

<6918 blocks left...

[phonglouis]

LeoB seems to be doing a pretty good job or promoting pascal. the community needs to grow
it's great tech... just needs to be in peoples radar
This coin needs marketing big time , otherwise going to remain as a sleeping giant forever

[Robin37s-]

so active recently

[tlaskows]

Dear PascalCoin users,

New PascalCoin Build 3.0.1

Build 3.0.1 - 2018-05-07
- Deprecated use of OpenSSL v1.0 versions. Only allowed OpenSSL v1.1 versions
- JSON-RPC Added param "openssl" on "nodestatus" call. Will return OpenSSL library version as described in OpenSSL_version_num ( https://www.openssl.org/docs/man1.1.0/crypto/OPENSSL_VERSION_NUMBER.html )

Please note:
- Linux users: Old versions of PascalCoin are (by default) running OpenSSL v1.1, you don't need to upgrade if you're using last release build 3.0.
- Windows users: By default PascalCoin was using OpenSSL v1.0, currently deprecated, this is mandatory to UPGRADE in order to use OpenSSL v1.1

You will find source code on Github:
https://github.com/PascalCoin/PascalCoin/releases/tag/3.0.1

Binaries also at Github or at SourceForge:
https://sourceforge.net/projects/pascalcoin

Remember: Hard fork activation at block 210000, probably on Thursday, 31-May-18
Mandatory upgrade to Version 3 prior to block 210000

That means those upgrades are only mandatory for Window users.
Anyway, thanks for your time to fix all technical issues and composing new wallets with more adjustments for the PASC community.

Google translate or completely random reply?

I'm a big time Windows fan.

Been using Linux almost exclusively since Slackware.

[thedreamer]

I'm a big time Windows fan.

Been using Linux almost exclusively since Slackware.

Umm... sooo which one is it? One or the other??

[tlaskows]

I'm a big time Windows fan.

Been using Linux almost exclusively since Slackware.

Umm... sooo which one is it? One or the other??

Good question.

Wallet version 3.0.1 is essential for Linux users.

Linux version used an outdated SSL library.

If you use Windows, no need to upgrade.

The wrong version of SSL 'could' potentially cause issues.

[tlaskows]

Can I join in now? How can I participate in ?

Yes,

It's never too late to join.

The official site has all the information.

http://www.pascalcoin.org/

There is a "Get Started" link there.

You can participate in many ways.

Running a full node, contribute to the code on github, etc.

[timmeyh]

A promising project indeed.
You know.  I spend hours reading on the subject, I really think that this one may have a great future ahead of it.
It's just my take though.  I'm not a crypto expert by any means.
Good luck to all of backers/devs!

[tlaskows]

A promising project indeed.
You know.  I spend hours reading on the subject, I really think that this one may have a great future ahead of it.
It's just my take though.  I'm not a crypto expert by any means.
Good luck to all of backers/devs!

Please stop spamming with ads in your signature.

I clicked on the link for the 'ico sale', 'next gen cryptocurrency'.

And that website choked a MacBook Pro running Linux with GPU acceleration enabled.

True story.

[sabine80]

Dear PascalCoin users,

New PascalCoin Build 3.0.1

Build 3.0.1 - 2018-05-07
- Deprecated use of OpenSSL v1.0 versions. Only allowed OpenSSL v1.1 versions
- JSON-RPC Added param "openssl" on "nodestatus" call. Will return OpenSSL library version as described in OpenSSL_version_num ( https://www.openssl.org/docs/man1.1.0/crypto/OPENSSL_VERSION_NUMBER.html )

Please note:
- Linux users: Old versions of PascalCoin are (by default) running OpenSSL v1.1, you don't need to upgrade if you're using last release build 3.0.
- Windows users: By default PascalCoin was using OpenSSL v1.0, currently deprecated, this is mandatory to UPGRADE in order to use OpenSSL v1.1

You will find source code on Github:
https://github.com/PascalCoin/PascalCoin/releases/tag/3.0.1

Binaries also at Github or at SourceForge:
https://sourceforge.net/projects/pascalcoin

Remember: Hard fork activation at block 210000, probably on Thursday, 31-May-18
Mandatory upgrade to Version 3 prior to block 210000

thanks for the new update. i'll do it right away. i am always happy about an update. it shows that this is an active project with an active dev.

[tlaskows]

Dear PascalCoin users,

New PascalCoin Build 3.0.1

Build 3.0.1 - 2018-05-07
- Deprecated use of OpenSSL v1.0 versions. Only allowed OpenSSL v1.1 versions
- JSON-RPC Added param "openssl" on "nodestatus" call. Will return OpenSSL library version as described in OpenSSL_version_num ( https://www.openssl.org/docs/man1.1.0/crypto/OPENSSL_VERSION_NUMBER.html )

Please note:
- Linux users: Old versions of PascalCoin are (by default) running OpenSSL v1.1, you don't need to upgrade if you're using last release build 3.0.
- Windows users: By default PascalCoin was using OpenSSL v1.0, currently deprecated, this is mandatory to UPGRADE in order to use OpenSSL v1.1

You will find source code on Github:
https://github.com/PascalCoin/PascalCoin/releases/tag/3.0.1

Binaries also at Github or at SourceForge:
https://sourceforge.net/projects/pascalcoin

Remember: Hard fork activation at block 210000, probably on Thursday, 31-May-18
Mandatory upgrade to Version 3 prior to block 210000

thanks for the new update. i'll do it right away. i am always happy about an update. it shows that this is an active project with an active dev.

Good luck with the update!

It took me 7 hours.  Old computer.  Intel Celeron 333 running XP.

[kuduirt]

sorry guys but polo alts death
binance now hv 1st for alts hehe
add on this place or nobody ll trade