Dear PascalCoin users, New PascalCoin Build 2.1.5Available source code at Github (Release 2.1.5), also available compiled binaries at Sourceforge (Windows installer / Linux binaries) Windows installer/Binaries at Sourceforge: https://sourceforge.net/projects/pascalcoin/filesRelease at Github: https://github.com/PascalCoin/PascalCoin/releases/tag/2.1.5### Build 2.1.5 - 2018-02-09 - GUI changes: - Allow massive accounts "change info" operation - Added "account type" and "sale price" on accounts grid - Show "account type" stats on search account form - Changed Icon to current PascalCoin icon - Pending operations buffer cached to file to allow daemon/app restart without losing pending operations - Less memory usage thanks to a Public keys centralised buffer - JSON-RPC changes - Added param "n_operation" to "Operation Object" JSON-RPC call - New method "findnoperation": Search an operation made to an account based on n_operation field - Params: - "account" : Account - "n_operation" : n_operation field (n_operation is an incremental value to protect double spend) - Result: - If success, returns an Operation Object - New method "findnoperations": Search an operation made to an account based on n_operation - Params: - "account" : Account - "n_operation_min" : Min n_operation to search - "n_operation_max" : Max n_operation to search - "start_block" : (optional) Block number to start search. 0=Search all, including pending operations - Result: - If success, returns an array of Operation Object - New method "decodeophash": Decodes block/account/n_operation info of a 32 bytes ophash - Params: - "ophash" : HEXASTRING with an ophash (ophash is 32 bytes, so must be 64 hexa valid chars) - Result: - "block" : Integer. Block number. 0=unknown or pending - "account" : Integer. Account number - "n_operation" : Integer. n_operation used by the account. n_operation is an incremental value, cannot be used twice on same account. - "md160hash" : HEXASTRING with MD160 hash - Solved bug that caused to delete blockchain when checking memory - Solved bug in Network adjusted time on receiving connections caused by full entry buffer - Minor optimizations
|
|
|
One of the worst team in the crypto-space for sure, good job Albert!
Your supossed to lead the team not be the team.
Albert have made a coin, but he doesn't owe you or any other person anything. If people need something, then they should do something about it. Yes. I've made a coin, I'm a dev, not a CEO. That's not a ICO coin, that's not a copy/paste quick-rich scheme... That's a new technology made from scratch, needs time and early adopters, and we're in the good way. Things will happen caused by users necessity, and changes will happen caused by users necessity too
|
|
|
I cant see the benefits of a deletable blockchain. What is this all about? Isnt it the core feature of a blockchain to be undeletable?
Do you need to know Joe bought a coffee for 3 btc in September 2009 ? I dont think so, thats why deletable blockchain (as a feature, not an obligation) is useful. Nobody needs the whole chain to use PascalCoin, but you can keep it if you want, if you are a merchant or just want to verify all, but thats not an obligation and it allows low end computers to download less blocks, sync faster and be light peace Very well explained. Deleteable Blockchain is a FEATURE, NOT AN OBLIGATION That's thanks to a new crypto-struct called "Safebox", that allows to control double spend without history transactions, one of the new features of PascalCoin
|
|
|
I love this coin and also hate it!
This tech is insane and could be used for many applications and transactions, many here know that.
So tech = perfect, Dont forget that people!
What i hate really is the skills of the team outside developing, so i more aim at the communication and design part of the coin.
-There is no team or management, discord is lead by mods that are not really part of the team. -No roles known by the community we know that Albert and Herman are lead devs, Nolan takes care of design (but how and what he is planning is vague). -Nolan works on the design but we seen close to 0 communication about this to the community, dont forget team people are supporting you with there own money get them involved. -No communication manager or maybe you should see the mods like that but spoke to some of the mods they dont really know the team aswell (insane if you ask me). -Roadmap is vague, they might be working hard but serieus make a roadmap that makes sense to people. -People are making designs without really having any feedback if its needed or if they want it or like it (again mods of discord do help here again) -Team unknown
I think if i would take more time i would come up with many more things, and no im not here to Fud i passed that stage in 2013! This is just serieus stuff people should think about if you wanna compete with the top coins and wanna be one of the crypto that will still exsist after a while.
Agree with you Will change this 2018, please give us some months (please note we're not a ICO/company, just early adopters, we need some time to self-organize and clear roadmap/rolls define) Thanks for suggestion and support, you're right: tech = perfect, Dont forget that people!Albert M.
|
|
|
Is this dead yet? Or can we still count on the dev-team & hope news from project?
Yes. Still here, and every day more people involved. Happy 2018!
|
|
|
Dear PascalCoin users, New PascalCoin Build 2.1.3Available source code at Github (Release 2.1.3), also available compiled binaries at Sourceforge (Windows installer / Linux binaries) Windows installer/Binaries at Sourceforge: https://sourceforge.net/projects/pascalcoin/filesRelease at Github: https://github.com/PascalCoin/PascalCoin/releases/tag/2.1.3### Build 2.1.3.0 - 2017-11-15 - Fixed BUG when buying account assigning an invalid public key - Added maxim value to node servers buffer, deleting old node servers not used, this improves speed - Re-add orphaned operations back into the pending pool - RPC locking to prevent N_Operation race-condition on concurrent invocations - Minor bugs
|
|
|
i guess it will start to rally again soon,
I don't know you know these coins are totally controlled by exchange and devs, the affect of investors is just a copy of the moves from exchange and devs, yesterday so many buy orders were dumped in seconds, some1 was sitting there with 300k pasc and selling no mather what price no mather how much, no investor buys so many coins to dump it at -20% , you have to be the exchange cooperating with the dev to totally control the price to make the curve like you want it to go to earn money in every up and down, even if a coin is undervalued it will x2 fast and lose 50% and make x3 and lose 60 % and so on, with this knowledge you drive the price high and you have more coins !
Please note: This is not an ICO or premine coin. Devs (me for example), have no more coins than others early adopters. I can't speak for exchanges, IDK, but I can speak for devs.
|
|
|
Interesting project
Good luck!
|
|
|
So did anyone answer to all questions from Bittrex?
Bittrex does not coins to discuss listing application status
|
|
|
For people asking to be listed on Bittrex (or other exchanges):
To be listed on bittrex or not is a BITTREX exclusive decision. They list coins based on multiple criterias, such as demand or people asking for them (on twitter, or slack or other channels)
So, for people using bittrex that wants to be listed there, you must ask directly to Bittrex team.
Thanks
|
|
|
i have an offer on column N Oper.
despite the deleted blocks, the number of operations for each account is displayed completely (see the fig.).
i propose to synchronize the number of operations with the total number of operations, which is displayed in the right column.
N Oper. in the left are outgoing operations made by the wallet user. Operations in the right are all operations both outgoing and incoming if you have the complete blockchain else it will be all operations in the incomplete blockchain. But I think you are right. It would be more logical if N Oper. was the total operations n_operation is an incremental and internal number that cannot be modified unless a new operation is executed by this account (for example, receiving coins does not modify n_operation on receiver account, only on sender) For technical reason it cannot be syncrhonized, because n_operation is responsible of preventing double spend with zero confirmation (and other things)
|
|
|
Hosting a fundraiser for notoriety would not be bad or "selling out." Your tech is incredible and solves a lot of problems than most even know. I'd gladly donate
Thanks. Currently there is a "key team" working for PascalCoin, we're all early adopters. At this moment we don't have a fundraiser, but we're working to increase marketing/promotion about PascalCoin technology If you want more info, join slack channel http://www.pascalcoin.org/slack-self-invite/
|
|
|
I don't get it. What is the exact point/reason for Pascal Lite?
forks are inevitable. so more forks mean pascal is more solid. what is the rationale behind this? How does forking benefit to 'the first and the only' pascal?this is in some way a measure of recognition of the success of a coin. IMO there is no battle between PascalCoin and clones. The real battle is between PascalCoin technology (Safebox) and traditional Blockchain technologies (bitcoin clones) Safebox offers a unique infinite scalling model that, once discovered by experts, will open a new era in altcoins Remember to visit www.PascalCoin.org for more info
|
|
|
|