Topic: [ANN] [PASC] PascalCoin, true deletable blockchain - V3 Hardfork on block 210000 - page 33. (Read 990744 times)

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

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

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.

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

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

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 !!!

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.

They have not been...

Unless you have an account that is full of PASC.

Accounts were selling for few PASC at pascwallet a long time ago.

I think I traded 20 PASC for a 4 digit account.

Not sure, but it was around 5$ in fiat at that time.

Can't.

That's CPU solo miner.

The first GPU miner (solo) was written by someone and it was for AMD cards only, I think.

It was only good right when this coin was released.

Go to official website and read the instructions.

Nanopool, or coinotron.

Pool only and many many GPUs if you actually want to generate some coins.

Look at what to mine (PASC)

I was doing 8GH/s in Feb, March of 2017... then I stopped.

You will see why....

I tried to post something the other day, but have not had internet access nor time.

There is no graphical version glitch on Linux wallet.

I'm running it on an intel atom x7, works 100%.

I had it USB tethered to update to 2.1.9.



Budget 400$ laptop.  Same with the phone.

@Jason likes my techniques.

i have a problem with the miner

i cant start mining, i have an nvidia gtx 970 card, but the miner doesnt start

PascalCoinMiner.exe -s localhost:4009 -p 0 -d 0 -n testname

i tested a lot of variations but no one works.

I know from my own experience that selling accounts for FIAT money is profitable. But you need to make some scripts to make it automatic.

At what point will the accounts trading become worthwhile?
Pascal is an incredibly promising coin, seems like it got stunted out by the sudden pump on the polo add. Cant wait for it to stabilize out and start growing again.

Yup, an account that has coins in it can be sent fully loaded to an address.

If you sent an account to his public key he should get it. He may just need to click the box to view his accounts. If you sent it to one of your keys then you would get the account back. As far as I know, you send accounts and coins separate. So only one or the other at a time. If you sent an account with coins in it then you may have sent him all the coins in that account. I can not be sure though what you did, as I can not quite understand exactly what you are saying that you did.

A strong project and very independent! I am sure of it 100%! The only thing I would like to see brighter dynamics, colors, perhaps it will work with the public offline and online ...

Dev is happy.

Current version (1.0.4) works fine on my server for more than 30 hours, holding more than 70 clients connections without losing effectivity.
Detected more than 350 distinct connections in my server.

Good job miners!
Good luck miners!

Thank for your reply.

Official name is Pascalcoin.

Operations are not deleted, rather full history is not required for the network to operate.

Smart contracts are not on the roadmap.

It's possible to implement almost anything using the hundreds of well documented API calls.

I'm not clear what smart contracts are, but I don't see urgent requirement for such a feature.

So on as in what else is missing?

Pascalwallet, getpasa, and there was an European exchange that allowed to sell and buy small amounts using FIAT if my memory serves me right.


Those were pretty advanced already.  Implemented and operated by devs that were not even official dev team.

For these sort of questions I think there is discord. 

Jason is on holidays.  They get 3 month vacations in Europe.

Try asking 500 Francs pasc

With pascal,transactions data are deleted.
Is it possible to implement advanced features,e.g. smartcontract,and so on.?