Bitcoin Forum
June 21, 2018, 04:18:18 AM *
News: Latest stable version of Bitcoin Core: 0.16.1  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 [410] 411 412 413 414 415 »
  Print  
Author Topic: [ANN] [PASC] PascalCoin, true deletable blockchain - V3 Hardfork on block 210000  (Read 608055 times)
bountyhunter433
Jr. Member
*
Offline Offline

Activity: 58
Merit: 0


View Profile
April 27, 2018, 12:38:59 PM
 #8181

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

Upfinex: Use Anonymous Decentrilized Exchange
Visit Official Website for ICO Details (https://upfinex.com/)
1529554698
Hero Member
*
Offline Offline

Posts: 1529554698

View Profile Personal Message (Offline)

Ignore
1529554698
Reply with quote  #2

1529554698
Report to moderator
1529554698
Hero Member
*
Offline Offline

Posts: 1529554698

View Profile Personal Message (Offline)

Ignore
1529554698
Reply with quote  #2

1529554698
Report to moderator
The World's Betting Exchange

Bet with play money. Win real Bitcoin. 5BTC Prize Fund for World Cup 2018.

Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1529554698
Hero Member
*
Offline Offline

Posts: 1529554698

View Profile Personal Message (Offline)

Ignore
1529554698
Reply with quote  #2

1529554698
Report to moderator
1529554698
Hero Member
*
Offline Offline

Posts: 1529554698

View Profile Personal Message (Offline)

Ignore
1529554698
Reply with quote  #2

1529554698
Report to moderator
1529554698
Hero Member
*
Offline Offline

Posts: 1529554698

View Profile Personal Message (Offline)

Ignore
1529554698
Reply with quote  #2

1529554698
Report to moderator
mr.Belyavski
Jr. Member
*
Offline Offline

Activity: 168
Merit: 0

automated solution for budget ICOs


View Profile WWW
April 27, 2018, 12:42:44 PM
 #8182

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

★ https://sbcplatform.com/?ref_link=9OAF4 ★
we reduce ICO preparation prices down to $5000 ✅ ✅ ✅
t.me/SBCPlatform_ico
asd12.123162
Jr. Member
*
Offline Offline

Activity: 73
Merit: 0


View Profile
April 28, 2018, 12:38:12 AM
 #8183

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.

█≣≣≣ Triggmine ≣≣≣█
TOKEN SALE
up to 20% -off first two days of pre-sale
thedreamer
Legendary
*
Offline Offline

Activity: 1218
Merit: 1002

Go Big or Go Home.....


View Profile
April 28, 2018, 12:42:06 AM
 #8184

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.


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

Go Big or Go Home.
Rugosa
Full Member
***
Offline Offline

Activity: 136
Merit: 104


View Profile
April 29, 2018, 01:27:54 AM
 #8185

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.

Website        ◆◇◆◇◆◇◆◇ VELOX ◇◆◇◆◇◆◇◆     ANN Thread
Whitepaper  The Future of Anonymous Trading    ◆ Twitter         
Discord        ◇◆◇◆◇◆◇◆◇◆◇◆◇◆◇◆◇◆◇◆◇      ◆ Telegram     
nightraven
Full Member
***
Offline Offline

Activity: 222
Merit: 100



View Profile WWW
April 30, 2018, 12:38:07 AM
 #8186

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.

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.

New PascalCoin Site: http://pascalcoin.frizen.eu
truong.bui45
Jr. Member
*
Offline Offline

Activity: 56
Merit: 0

Blockchain Just Entered The Real World


View Profile
May 01, 2018, 02:53:54 AM
 #8187

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.

Q U A D R A N T  『 http://www.quadrantprotocol.com/ 』
A Blueprint for Mapping Decentralized Data
tlaskows
Full Member
***
Offline Offline

Activity: 336
Merit: 100


Join GANTECH’s team of game changers


View Profile WWW
May 01, 2018, 02:08:02 PM
 #8188

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.




GANTECH | End-User Computing Solutions
http://gantech.net/who-we-are/our-leaders/
tlaskows
Full Member
***
Offline Offline

Activity: 336
Merit: 100


Join GANTECH’s team of game changers


View Profile WWW
May 01, 2018, 02:12:18 PM
 #8189

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.


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

GANTECH | End-User Computing Solutions
http://gantech.net/who-we-are/our-leaders/
tlaskows
Full Member
***
Offline Offline

Activity: 336
Merit: 100


Join GANTECH’s team of game changers


View Profile WWW
May 01, 2018, 02:18:12 PM
 #8190

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.

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.




GANTECH | End-User Computing Solutions
http://gantech.net/who-we-are/our-leaders/
jmknapp80
Full Member
***
Offline Offline

Activity: 182
Merit: 100


View Profile WWW
May 01, 2018, 11:48:13 PM
 #8191

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

tlaskows
Full Member
***
Offline Offline

Activity: 336
Merit: 100


Join GANTECH’s team of game changers


View Profile WWW
May 02, 2018, 01:55:12 AM
 #8192

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.


GANTECH | End-User Computing Solutions
http://gantech.net/who-we-are/our-leaders/
PascalCoin
Sr. Member
****
Offline Offline

Activity: 300
Merit: 260



View Profile
May 02, 2018, 02:49:22 PM
 #8193

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

PascalCoin is the first crypto currency without need of historical operations to control double spend and with ORDINAL account numbers. YES! LIKE A BANK!
tlaskows
Full Member
***
Offline Offline

Activity: 336
Merit: 100


Join GANTECH’s team of game changers


View Profile WWW
May 02, 2018, 02:54:37 PM
 #8194

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

Thanks.

I just upgraded recently to 2.1.9.

 I had no idea about the HF.

Too many things to keep track off.

Stick with $PASC FTW

GANTECH | End-User Computing Solutions
http://gantech.net/who-we-are/our-leaders/
tlaskows
Full Member
***
Offline Offline

Activity: 336
Merit: 100


Join GANTECH’s team of game changers


View Profile WWW
May 02, 2018, 03:48:26 PM
 #8195

Works great on my iMac Pro (I do professional video and photo for a living).

I even did a test OP between my accounts.

Transferred 7 PASC and it was finished in less than a minute (green circle).

Took 5 minutes to update.



If anyone needs support on how to use computer, please use discord.

 Grin




GANTECH | End-User Computing Solutions
http://gantech.net/who-we-are/our-leaders/
Blocktree
Full Member
***
Offline Offline

Activity: 168
Merit: 100



View Profile
May 03, 2018, 08:17:18 AM
 #8196

What about changing to a more POP name,not a coding name?
caffeman
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
May 03, 2018, 12:58:03 PM
 #8197

What about changing to a more POP name,not a coding name?
yeah,PascalCoin need a new brand,new name,shorter and closer.
tlaskows
Full Member
***
Offline Offline

Activity: 336
Merit: 100


Join GANTECH’s team of game changers


View Profile WWW
May 03, 2018, 03:12:54 PM
 #8198

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.

GANTECH | End-User Computing Solutions
http://gantech.net/who-we-are/our-leaders/
Skybuck
Full Member
***
Offline Offline

Activity: 204
Merit: 100


View Profile
May 04, 2018, 10:27:59 AM
 #8199

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

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

It's been mentioned on slashdot.org Wink

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 Wink Smiley
lieutkcb
Jr. Member
*
Offline Offline

Activity: 36
Merit: 0


View Profile
May 05, 2018, 09:44:50 AM
 #8200

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

Upfinex: Use Anonymous Decentrilized Exchange
Visit Official Website for ICO Details (https://upfinex.com/)
Pages: « 1 ... 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 [410] 411 412 413 414 415 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!