 Show Posts
|
|
Pages: [1] 2 3 4 5 »
|
Make sure your card is in p state 0.
It is, but p-state only affects memory clock and since x16r is irresponsive to it I doubt running P2 will make a difference even at -500MHz in AB which will make it 4000Mhz or so. At least I tried running 5500Mhz with GTX1080 and results were the same as with 4500Mhz. Sorry your right that's true for 1080. Makes a big difference on other cards for gpu intensive algos. |
|
|
|
Just updated drivers from 399xx to 411.70 on my home pc (win7) and noticed perfomance drop in x16r on my 1080. On my rigs I use win10 though, but still unsure whether update drivers or not. Probably gonna have to wait for miner update that improves perfomance with cuda 10.0 drivers
Make sure your card is in p state 0. |
|
|
|
Many developers create new coins only to seek their private interests, and hope that Cryptonite is not.
XCN is 4 years old and the developers aren't paid. Paid, what did you imply, e.nexus? XCN has amazing, creative ideas which can be further developed that in turn will boost the project to the Moon. By now, XCN has gone far distance from its beginning 4 years ago. I imply that it's not a new coin and the developers aren't seeking their own private interests. |
|
|
|
The wallet compiles well in Fedora 28 x64 and works perfectly, but because of the screen, the wallet and font are tiny. The wallet can't be resized (as with a huge amount of them I found out) on a 4K screen. Not complaining, just a fact I thought I would share. Almost nothing can be done from what I can see about it, unless the screen resolution is lowered, which defeats the purpose of having a 4K Screen in the first place.
HighDPI scaling support was added in the wallet's Qt updates. You can try starting the gui from a console with: QT_SCALE_FACTOR=2 ./cryptonite-qt |
|
|
|
Many developers create new coins only to seek their private interests, and hope that Cryptonite is not.
XCN is 4 years old and the developers aren't paid. |
|
|
|
About the "many gpu" issues of the miner, I will look into it ;-)
You are one in a million mate ... Thanks for that. Working on the compiles later tonight also, still can't get them sorted under both Fedora 27/28 x64 (due to many other factors - especially the updated gcc) and CentOS 7 x64, so we can start testing Obsidian (our stratum) properly under our new environment (Pyroxene (theMINE)). #crysx A fix has been applied for Fedora 28. The configure options will be: ./configure CPPFLAGS="-std=c++11 -fPIC" --disable-hardening --with-incompatible-bdb --disable-tests I'll check this out later tonight when I am able to ... it won't be long into the compile to see if it all works, though if that is the only setting that is required, then it won't be difficult to change it manually if need be. Now for the GPU limitation in the miner pallas has, and we will be set  CentOS 7 x64 is still giving us headaches with compilation, so if there is something that needs to be set there also, it would be greatly appreciated also. All the help currently is much appreciated. #crysx There were also changes to the code for boost1.66 so you'll need a new clone. I'll have a look at centos tonight. Already done - and compiles well ... Thanks for that. The wallet compiles well in Fedora 28 x64 and works perfectly, but because of the screen, the wallet and font are tiny. The wallet can't be resized (as with a huge amount of them I found out) on a 4K screen. Not complaining, just a fact I thought I would share. Almost nothing can be done from what I can see about it, unless the screen resolution is lowered, which defeats the purpose of having a 4K Screen in the first place. CentOS 7 x64 compile would be awesome, which would allow us to build and test our stratum (Obsidian) against it. I wonder if similar configure commands would be required to compile? Though CentOS 7 x64 has older versions of gcc and boost (not to mention OpenSSL crippling) which would probably fail. I haven't tried and I am running out of time to try tonight. Maybe tomorrow. This will open a new area of functionality for XCN in the backend, especially for us, so we will keep working on it. Being one of the CWI-Supported Coins, we will also have it on the CWI-WebSite when the section of the website is completed later this year. Have a good one. #crysx I added a fix for centOS 7. If it's not merged you can see in the pull reqs. Same config options as Fedora works. |
|
|
|
About the "many gpu" issues of the miner, I will look into it ;-)
You are one in a million mate ... Thanks for that. Working on the compiles later tonight also, still can't get them sorted under both Fedora 27/28 x64 (due to many other factors - especially the updated gcc) and CentOS 7 x64, so we can start testing Obsidian (our stratum) properly under our new environment (Pyroxene (theMINE)). #crysx A fix has been applied for Fedora 28. The configure options will be: ./configure CPPFLAGS="-std=c++11 -fPIC" --disable-hardening --with-incompatible-bdb --disable-tests I'll check this out later tonight when I am able to ... it won't be long into the compile to see if it all works, though if that is the only setting that is required, then it won't be difficult to change it manually if need be. Now for the GPU limitation in the miner pallas has, and we will be set CentOS 7 x64 is still giving us headaches with compilation, so if there is something that needs to be set there also, it would be greatly appreciated also. All the help currently is much appreciated. #crysx There were also changes to the code for boost1.66 so you'll need a new clone. I'll have a look at centos tonight. |
|
|
|
About the "many gpu" issues of the miner, I will look into it ;-)
You are one in a million mate ... Thanks for that. Working on the compiles later tonight also, still can't get them sorted under both Fedora 27/28 x64 (due to many other factors - especially the updated gcc) and CentOS 7 x64, so we can start testing Obsidian (our stratum) properly under our new environment (Pyroxene (theMINE)). #crysx A fix has been applied for Fedora 28. The configure options will be: ./configure CPPFLAGS="-std=c++11 -fPIC" --disable-hardening --with-incompatible-bdb --disable-tests |
|
|
|
It's 23 million not billion.  |
|
|
|
Updated Win64 Cross-Compile Guide For v0.1.6The Windows wallet is cross-compiled on Ubuntu or The Windows Subsystem for Linux. 1) Install the cross-compiler dependencies: sudo apt install autoconf automake autopoint bash bison bzip2 flex g++ g++-multilib gettext git gperf \
intltool libc6-dev-i386 libgdk-pixbuf2.0-dev libltdl-dev libssl-dev libtool-bin libxml-parser-perl lzip make \
openssl p7zip-full patch perl pkg-config python ruby scons sed unzip wget xz-utils 2) Download the wallet and cross-compiler sources: git clone https://github.com/pallas1/Cryptonite.git git clone https://github.com/e-nexus/mxe.git 3) Build the cross-compiler: make MXE_TARGETS=x86_64-w64-mingw32.static.posix db gmp boost libqrencode miniupnpc protobuf qtbase qttools -j4 4) Build the wallet: (Replace /path/to with the path to your mxe folder)PATH=/path/to/mxe/usr/bin:$PATH ./configure CPPFLAGS="-std=c++11 -fPIC" --host=x86_64-w64-mingw32.static.posix --with-qt-incdir=/path/to/mxe/usr/x86_64-w64-mingw32.static.posix/qt5/include \
--with-qt-libdir=/path/to/mxe/usr/x86_64-w64-mingw32.static.posix/qt5/lib --with-qt-plugindir=/path/to/mxe/usr/x86_64-w64-mingw32.static.posix/qt5/plugins \
--with-qt-bindir=/path/to/mxe/usr/x86_64-w64-mingw32.static.posix/qt5/bin --with-boost-libdir=/path/to/mxe/usr/x86_64-w64-mingw32.static.posix/lib \
--with-protoc-bindir=/path/to/mxe/usr/x86_64-pc-linux-gnu/bin --with-incompatible-bdb --disable-hardening --disable-tests The daemon and cli are in the src folder and the gui wallet is in the src/qt folder. WSL users can install a file manager using sudo apt install mc, then type mc in the console to run it and move your compiled wallet to the Windows file system under /mnt/c/.
|
|
|
|
pallas
It's strange. Finally my wallet became synced (it took 4-5 hours to sync 4000-5000 blocks)
So I wanted to experiment and deleted whole blockchain. After that wallet synced from scratch in 5-10 minutes. Very strange.
Now it shows my ammount of coins but in transactions - all are gray and with red flag telling "Unknown". Is it ok?
When you do that the number of confirmations is forgotten but your balance is fine. |
|
|
|
Hey people, what's the difference between the db48 and db61? Ty!
You can transfer your wallet file between OS if the wallet uses the same db version. Bitcoin maintains a repository for ubuntu with db4.8 so having a windows version makes it easier. If you only ever use windows then db6.1 |
|
|
|
Quietly potential  When I read ‘bout this project, I’m sure this is a potential project whether this project provides for the bounty hunter? I’m looking for not finding rules for bounty  2nd post has some. Join the discord server and get involved. |
|
|
|
I have bought a handful of coins to test network, but would somebody willing to test it setting up a 10-20 nodes to sent it to them simultaneously.
Without it, it's hard to test with 2-3 computers, throughput of network. I can't make a couple of VMs, but it won't be enough.
I am interested in such a kind of performance test and would like to participate, but in the next weeks I have not so much time for it. In mid to late April, it would be possible for me. I'll confirm in 2-3 weeks. It would be reasonable to use a test network for that. Is there currently a XCN testnet running? I don't think so but we can quickly set it up. Thanks. well, just using the live net would be doable, too. TX fees are literally nothing, so would be interesting to compare testnet vs live. I'm surprised about the initial report of having 8-10 min confirmation time. Whenever I did a transfer, it was visible the same instant (sent around the world, NZ -> Germany while talking on phone) and confirmed within the next block. Keep in mind that with withdrawal limits in place, technically, no confirmation is required and instant tx is possible. This feature needs more support in the wallet to be actually usable but the foundation is there! I don't know why it was like that maybe ot confirmed faster, but in client it showed first confirmation after 8 min, and I checked it. 5 confirmations more come in 5 min, so it was strange. Btw. do you think that if it would be rebranded, you could change from PoW to PoS? I mean 4 years distrubution is a lot, and PoS could be more robust, and more energy efficient. With 1 minute block times, when the global hash drops by 85% it will take that long until the diff lowers. |
|
|
|
I have bought a handful of coins to test network, but would somebody willing to test it setting up a 10-20 nodes to sent it to them simultaneously.
Without it, it's hard to test with 2-3 computers, throughput of network. I can't make a couple of VMs, but it won't be enough.
I am interested in such a kind of performance test and would like to participate, but in the next weeks I have not so much time for it. In mid to late April, it would be possible for me. I'll confirm in 2-3 weeks. It would be reasonable to use a test network for that. Is there currently a XCN testnet running? I don't think so but we can quickly set it up. Thanks. well, just using the live net would be doable, too. TX fees are literally nothing, so would be interesting to compare testnet vs live. I'm surprised about the initial report of having 8-10 min confirmation time. Whenever I did a transfer, it was visible the same instant (sent around the world, NZ -> Germany while talking on phone) and confirmed within the next block. Keep in mind that with withdrawal limits in place, technically, no confirmation is required and instant tx is possible. This feature needs more support in the wallet to be actually usable but the foundation is there! I think when they tested the diff was high and Mr 10GH had just left. |
|
|
|
what am i missing to import a XCN paper-wallet from within the new Windows wallet? i've been running 1.4.2 until today updated with the Cryptonite-0-1-5-db61.zip version.
i decided to send my XCN to a second laptop and install the db61 version (non backward compatible) then sent it back to the new empty wallet. worked fine, and still shows older transactions.
going to buy a couple Freiexchange shares too...
In console use: importprivkey [yourprivatekey] |
|
|
|
|
