On one of my machines the wallet says alone in the world and that my IP is blacklisted? I've got several machines running from the same public IP. Any idea whats causing this or a way to fix it?
Check you date/time and Time/Zone ... |
|
|
|
https://poloniex.com/coinRequestWas trying to fill out the form but missing too much information. Poloniex wants to know if the coin has a symbol and if it has an online block explorer? What else is needed to get on the exchanges. RPC access and Linux are complete now? What else? RPC is not complete. I'm working on it. Wait 1 week. |
|
|
|
OpenCL miner is here!
Aplause! Very good job Vorksholk! |
|
|
|
next step for pascal is pool  It's like developing for Bitcoin all over again, very happy that the community is making strides and the pascal developer is pushing out continuous and serious updates. I believe this project has huge potential because of it's correlation with cryptography and typical legacy system infrastructure. Mr. Satoshi Nakamoto did not had a furious comunity like yours in first 2 months of Bitcoin life ...  I'm developing all over again, it's true, but I'll not develop apps for third partys use. For example: App for a pool. I'll only develop RPC calls to be accessible for third partys (exchanges, pools or new kind of applications based on account system of PascalCoin) If somebody wants to create a pool, will need to develop itself a pool server, like Vorksholk developed a GPU miner. |
|
|
|
Hi everybody. I've found an explanation about why PascalCoin is allways "discovering servers" and It's difficult to connect: It's a Bug In few hours I'll update version build to 1.0.9 correcting this issue (now I'm testing). It's important that everybody update it too to make PascalCoin network more stable.Affected versions are 1.0.6, 1.0.7 and 1.0.8 (earlier versions don't have this bug... but they have "other" bugs). Of course Vorksholk binaries have this bug too, I'll talk with him to arrange it. The dev. Hey, figured I'd just write a proxy that connects to 1.0.9 and ferries the necessary data to a usable form for the CUDA miner, and then ferries results back. But when I submit a nonce like "3791967799" (bigger than 2^31 but smaller than 2^32) to your client, it is rejected for not being an integer, despite being smaller than 2^32. Did you use a signed integer instead of an unsigned integer for this? These nonces never had an issue before. If you can make a release that allows the full nonce range (up to 2^32), then everyone can GPU-mine with multiple GPUs to one wallet using the proxy I'm making. Try StrToInt64 instead of StrToInt, mask out the extra 32 bits, and put it in a Cardinal? One solution is sending a signed 32 bits value. So value 0..2147483648 are positive and values 2147483649..4294967295 are equals to -2147483647..-1 Int32(-2147483647) = UInt32(2147483649) Int32(-1) = UInt32(4294967295) Just convert a Uint32 to Int32 and send it at "nonce" value |
|
|
|
What does this mean:
"Op 1/1:sender (XXXXXX) is blocked for protocol."
Can't seem to transfer funds from some of my mined accounts.
You must wait 100 maturation blocks prior to send or receive coins, or to change key... |
|
|
|
How do you mine with the new wallet ?
CPU mine? or GPU Mine? Build 1.0.7 was created without CPU miner because introduced a JSON-RPC server for miners. (also, build 1.0.8 and 1.0.9) There will not be mining possibilities directly from the Wallet. Are you interested in CPU mining? |
|
|
|
New PascalCoin Build 1.0.9Full source code (MIT license) at Github: https://github.com/PascalCoin/PascalCoinWindows installer and Ubuntu Desktop 16.04 Binaries at SourceForge: https://sourceforge.net/projects/pascalcoin-------------------------- Build 1.0.9.0 - 2016-10-21 -------------------------- - Corrected a BUG (BUG-101) that causes blocking connections when received more than 100 connections, causing "alone in the world" after a cert period time and also "Discovering servers" state. - It's necessary to update because new version will connect first with same version to make network stable. Remember... if you enjoy it... make a donation to the project: BTC 16K3HCZRhFUtM8GdWRcfKeaa6KsuyxZaYk Grin
|
|
|
|
Hi, first of all thanks for the input. Second, if Vork is busy with OpenCL miner and/or real life business would it be possible that you would release a "out-of-the-factory-patched" version to work with the miner? I know I'm asking for a little too much, but maybe you have some spare time to help us here mine with the new stable version (until miner with JSON-RPC support is released). Cheers & keep up the good work! I don't have Vorksholk modified source code... so... I can't build Vorksholk version. |
|
|
|
Hi everybody. I've found an explanation about why PascalCoin is allways "discovering servers" and It's difficult to connect: It's a Bug In few hours I'll update version build to 1.0.9 correcting this issue (now I'm testing). It's important that everybody update it too to make PascalCoin network more stable.Affected versions are 1.0.6, 1.0.7 and 1.0.8 (earlier versions don't have this bug... but they have "other" bugs). Of course Vorksholk binaries have this bug too, I'll talk with him to arrange it. The dev. |
|
|
|
Developer, Nice job on the Linux version, it installed nice with your instructions! As you say, the access database has been replaced. Does that mean there is no longer a way to view the database?
Thanks
Due to be "cross-compatible" i've made an own file database without using third party libs (no ADO, no MySQL, no Access...) If a third party dev wants to explore PascalCoin database file, must create it's own soft based on source code of file "UFileStorage.pas" that can be found at github |
|
|
|
There are two specs for buffer_payload
One says ASCII from 23 to 255
The other says 32 to 254
Is this a typo or am I missing something?
Ops! I've corrected github file. Correct text is: Only from ASCII from 32 to 254 Thanks! |
|
|
|
Will this code make it easier to fit it into the exchanges pipeline?
Of course! For an exchange is MANDATORY that PascalCoin runs over Linux. Now it's possible! (But of course... I need to add RPC calls... wait for the next build) |
|
|
|
Is it compatible with the miner or is it a stand alone wallet?
This is a stand alone wallet with RPC-JSON server for GPU miners developers. If a GPU developer wants to use this Wallet to mine, must follow instructions that can be found at Github |
|
|
|
|
Note about linux binaries:
Sorry... linux users... I don't know how to make a .deb file for automatic installation... you can follow my instructions included in "PascalCoin_1.0.8_Ubuntu_16.04_Binaries.tar.gz" or compile source code following instructions you can find at Github
If somebody knows how to make an Ubuntu Installer... Please PM me. Thanks
|
|
|
|
New PascalCoin Build 1.0.8 - CROSS COMPATIBLEWorks with Windows and LinuxFull source code (MIT license) at Github: https://github.com/PascalCoin/PascalCoinWindows installer and Ubuntu Desktop 16.04 Binaries at SourceForge: https://sourceforge.net/projects/pascalcoinBuild 1.0.8.0 - 2016-10-20 -------------------------- - Cross compatible - Can compile with Delphi or Lazarus (Free Pascal) - New storage system. No more access database - Network hashrate calculation Remember... if you enjoy it... make a donation to the project: BTC 16K3HCZRhFUtM8GdWRcfKeaa6KsuyxZaYk
|
|
|
|
What wallet is 1.0.8w? I seem to not be getting the latest blocks from the chain. I see someone using that wallet version on a server. Is it the linux version?
It's the New version... I'm going to upload Windows installer, Linux binaries and source code and "how to compile" instructions. Works with Windows and Linux |
|
|
|
What's the estimated time for each block ? The time the difficulty tries to adjust itself to?
5 minutes. True. But 5 minutes are a "theorical" average. Core is designed to addapt it's difficulty on each block with previous 100 blocks time average and with a higher decreasing difficulty than increasing difficulty. The result is that when hash rate is changing quickly average time is a value between 4 and 5 minutes. |
|
|
|
I'm guessing you're calculating MH from the time it takes to solve the block and not actual hash rate of the miner in question?
Yes. Mh/s is calculated based on average to solve last blocks. It's the network hash rate |
|
|
|
|
Show Posts
