Pascal Coin: Crypto currency without need of historical operations

  • Protect yourself from scammers ! and use Skybuck's PascalCoin version (may also include FireMonkey GUI/Interface in the future):

    The mentioned account number 3516 is banned from performing operations in this version. (Current account balance: 59,509.2737) (Current account name: millionaire) (operations: 36) 

    He may have other accounts as well but for the time being I will let these be, but these are also highly suspect: 

    317372-75  (Seems to be a backup account of his) (Current account balance: 3000) (Current account name: <empty>)  (operations: 6) 
    3490-60 (Seems to be a fund raising account, could be a scam of his) (Current account balance: 1100) (Current account name: fundraising) (operations  7)

  • Pascal Coin is going to upgrade to V3. Vote on PascalCoin V3 proposals 

    V3 Roadmap Vote (BETA)

    Vote on PascalCoin V3 proposals. This is a BETA release, but vote numbers will not change, so vote now if you want.

    Details :


    Albert Molina — Creator of PascalCoin interviewed the “Satoshi” behind PascalCoin, Albert Molina, where he shared his plans about the future, the story behind the project and the SafeBox technology, plus he shared Pascal’s Coin opportunities for improvement in the future.

    Because the interview was in Spanish we would like to provide you with the English transcript of it. You can find the full interview at the end of the article.


    • Why do you think that most crypto currencies cannot find the key to implement scalability?

    Whether luck or not, pascal was born as a project from scratch, giving the freedom of creating a different block-chain structure without using the btc code and hence allowing a new safebox structure to solve scalability, which as we know, is very difficult with btc, this is an important factor … when created from 0, it allowed the luxury to envision how it could grow without major underlying problems in the future, unlike what we are seeing in btc …

    SafeBox -The technology that allows Pascal Coin to get infinite scalability
    • What were your thoughts when you learned that PascalCoin was being mined by the Ethereum miners?

    I was very concentrated in the development, so it took me a while to find out, at the beginning it stroke me as a positive thing as I thought those who mine eth also dedicate resources to pascal, with time, we’ve obviously realized that something must be done to address this issue… the least known currency is the one that loses when one aces dual-mining… there are proposals so that there is no mining dual … we are at a point where everything is not perfect but we have some clear roadmap to fix it.

    • What is your vision of Pascal within 1 year?

    I want to see a natural evolution similar to what we have experienced in the last year, growth due to the technology that Pascal uses (safebox) and thanks to it that the code could implement new functionalities and the knowledge grows … obviously we depend on the massive use, therefore , we must provide third-party applications. Also the diffusion of content explaining how it works and its advantages and general knowledge of the technology.

    • Question from @CryptoBigDawg: How would you compare Pascal with the rest of crypto currencies nowadays? For example bitcoin, nano etc. An important feature for mass adoption is usability — are you working to make the user experience the ideal one to achieve this goal? Are you working to make the user experience the right one?

    This is one of the expected changes in the immediate future, the user experience. Bank-type accounts in Pascal are an advantage, but if it is true that the wallet is very technical and not visual enough, this is the most important part … it must be very intuitive, easy access, similar to the existing ones while keeping the technical part intact.

    • What kind of advantage do you think it gives you to be the first crypto currency to solve the problem of scalability?

    I hope it gives us an advantage … being the first is not an advantage in itself, but not only the first, but being in constant evolution and adapting to new needs, we personally achieve that as Pascal can interact with layer 2 protocols so that thanks to a single application you can have different interconnected. Since we have already solved part of the problem with scalability, it allows us to anticipate in the present future problems that may exist.

    • What are all the advantages of programming with the FREE PASCAL code? The language is not important but if it allows you to do what you are interested in is. I like Pascal’s functionalities and its interoperability and also as a language that can be compiled natively for any chip, unlike other programs. I am interested in being able to use pascal node in very simple machines, so that is not necessary to be installed on large servers, and this gives an advantage over other cryptos that require greater memory capacity, this in pascal is very fine tuned and works in very simple machines …

    • The scalability has been solved with the ‘safebox’, have you done more tests of stress in transactions per sec? ¬ Could you clarify what is the maximum number of transactions that Pascal can get per Second? In theory, based on the design, what would be the maximum that could be expected?

    A machine with a single cpu and that is where the nodes run, and 1 or 2 gbs of ram, transactions of 1,000 / sec are achieved … how much can it grow? It will depend if we add CPU technology, processors, so that transactions are much faster. Why 1,000 per second? Thanks to the safebox. The maximum would depend on the amount of hardware, video cards, multiple cpus, parallel processing. We have not performed stress tests with larger machines, for the moment only in very simple machines … stress tests have all accepted 1,000 / sec easily … although theoretically we can grow much more, but I cannot you a figure.

    • How and when does PascalCoin plan to implement zk-SNARKS?

    It is not a priority since it requires a deep analysis that I have not yet been able to perform.

    • @Rektoshi: Could the same concept of the safebox be written in another programming language? Why Pascal and not C ++ or another language with more use of programmers? Do not you think this limits the development via open source / open source?

    Pascal is a language I dominated perfectly … it was the most natural way to write it. if I had started with C from 0, maybe I would not have done all the code from scratch nor created the safebox, thanks to this approach it helps us solve the problem of scalability. Yes, it is true that it would be easier with C, but maybe in the future we can rewrite in another language. There is already a very important community but in percentage terms it is very inferior, although I must say that there are still enough and the language of pascal is not so didactic but more visual and easily accessible, easily educational too.

    • @Tommyworldpower: When do you expect to have the new algorithm available to mine Pascal?

    The new algorithm is a proposal by Herman (random hash) that solves the problem of mining and the theoretical part is written, as it is a proposal of Herman, so I prefer that he is the first to implement and talk about the new algorithm. We need to conduct a thorough analysis if can be implemented and what benefits or inconveniences we may face. For now, I can say that it will not be implemented soon (in the next revision) unless everything goes very fluid … the factor of mining must also be taken into account … the mining must be sufficiently distributed among several miners but without reaching an extreme that is too random, since this leads to the risks of orphaned blocks .. if they do not use a pool and instead their own machines, the collateral damage that occurs is that there are many orphaned blocks and that is good, since it is important that it remains consistent, that the operations that are introduced do not suffer variations, that is why any implementation must foresee all the scenarios. I am a supporter but I would not like to forecast a date as it requires a deeper analysis.

    • With the implementation of PIP-0011, what are the most immediate actions that are going to be undertaken in relation to marketing? How do you expect Pascal to be better known?

    The funds that will exist on the PIP-0011 will be for marketing and development, as well as the new mining algorithm down the road. The most important thing is how this fund is managed. We must propose a fund management mechanism with a legal structure such as a foundation with propoer coverage so there are no problems nor doubts that we are only going to benefit the community. About the marketing plan: The diffusion of Pascal in large exchanges is our main goal, this is the grand objective that Pascal must have. I also must say that the UK exchange where we were listed holds some bright future. We want to achieve new listings via the image of seriousness, integrity of the team, the technology we provide, that there is a plan for the future, sense of unique project. This is the orientation that we should have for the marketing to generate enough confidence

    • What makes other cryptos such as IOTA or NANO have such a huge capitalization in front of Pascal? Do you think it’s just a marketing question?You do not think that based on the industry’s standards, the project has an extremely low capitalization.

    Although I do not know their technology in depth (Iota, Nano), there are 2 factors that have helped them, the first reason is that they are included in different exchanges and then the marketing campaigns that have been launched. They have done a great job combining both, that is, a good technology and good marketing campaign. Pascal can also experience this growth cycle. Comparatively, it is nonsense that there is such a large disparity in market cap (Pascal 20–25million range vs billions in Nano or Iota) or even with others that do not offer technology but only marketing. The factor of only listed in one large exchange is very limiting for now.

    • What is the current activity and commitment in the development of PascalCoin?

    Since a few weeks ago we have been exclusively focused on the evolution of the implementation of the new Pascal hardcore with new features that were voted after proposed pips. The intention is that all pips will be implemented or as worst case, only those that we consider to be safe as explained before. The objective is to grow the currency. Now we have 3/4 developers and before 2 months we are expecting to be able to offer the solution and the implementation of version 3.

    • Are there actions to be added in new exchanges? Do you not consider it a risk that the only renowned exchange is Poloniex?

    I have contacted Poloniex and there is no concern at all, they have provided re-assurance. Actually, the opposite is true, the acquisition of Poloniex by Circle offers a great advantage as the exchange will evolve into a large professional and fully regulated entity that will provide a bridge for institutional capital to come into the space, and that will benefit Pascal. Lastly, I want to thank the entire community at Pascal for all the involvement and commitment. I am convinced that we will go much further. Pascal coin technology has a lot to offer. In the short term, marketing alone can give you a temporary boost but in the long term, only those who combine marketing + technology will really go far and Pascal is one of these projects, no doubt.

    Check out the Video Version of the interview on:

    Our team would like to thank for the great interview they done.

    Also do not hesitate to send your question via and some of them will be answered by the new Satoshi — Albert Molina :).

    Official Links PascalCoin website: Discord: Telegram official channel: Twitter official account: Reddit: Medium -PascalCoin:

    For those who are not familiar with this project:  - What is PascalCoin? (official video)  - What is Pascal? (review)  - Instant Transfer :  - Comparison : - PascalCoin Guide for Beginners:

  • PascalCoin (PASC) Release New Build 2.1.7

    Build 2.1.7 - 2018-04-10

    • Remove use of TPCOperation.FSignatureChecked introduced on 2.1.6 because is not 100% secure
    • Minor bugs


  • PascalCoin Testnet V3.0 release of CORE and CLASSIC WALLET GUI


  • PascalCoin Release New Important Build 2.1.9


    Build 2.1.9 fixes some importants bugs detected from all previous versions related to BlockChain file corruption. UPGRADE

    Build 2.1.9 - 2018-04-16

    • Searchs last valid block found on corrupted BlockChainStream.blocks file and allows to continue from last valid one. On prior versions, app halted and needed manually file deletion
    • Solved bug that can cause to corrupt BlockChainStream.blocks file when detecting an orphan block and creating new BlockHeaders row (every 1000 blocks). Very rare bug, but fatal erro


  • PascalCoin (PASC) Release Testnet 3.1 - (2018-04-19)

    PascalCoin TESTNET version 3.1 

    If you're running OLD testnet version, please remove ALL blockchain/safebox files prior to test 3.1 Version 3.1 contains a new target calculation method incompatible with TESTNET 3.0

    Blockchain files are at: /$HOME/PascalCoin_TESTNET/Data Windows: c:/Users/ (my user) /AppData/Roaming/PascalCoin_TESTNET/Data

    Source Code:

  • PascalCoin [PASC] Testnet Update V3.2

    Source code

  • PascalCoin (PASC) Release New Build v3.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)
      • 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


  • PascalCoin Release New Build 3.0.1

    Build 3.0.1 - 2018-05-07

    Please note:

    • Linux users: Old versions of PascalCoin are (by default) running OpenSSL v1.1, you don't need to upgrade.
    • Windows users: By default PascalCoin was using OpenSSL v1.0, currently deprecated, this is mandatory to UPGRADE in order to use OpenSSL v1.1


Log in to reply

Looks like your connection to Cryptocentral was lost, please wait while we try to reconnect.