Get lost... Of course Cezarysw is nothing more than Cezarysw:  |
|
|
|
Hello
386.5 ETH was stolen from my Ledger Nano S
Yeah, sure. Btctalk rookie with 386 ETH. Keep going... |
|
|
|
|
I can confirm lower CPU usage of 1.3.2 and 1.3.3 Qortal core. I'ts around half of what it was with previous versions. Even UI is now more responsive with lower CPU usage of the core.
|
|
|
|
Core updated, confirmed update of UI. Syncing was bad and after core restart suddenly stopped working. Tried temporary version and got same errors:  EDIt: better explanation Fixed with complete deinstall/install of Core and UI. BTW, latest UI (1.2) was not possible to install, double clicking installation exe did nothing. Installed older version of UI and did upgrade afterwards. Conclusion: Qortal is not working as it should on 64-bit WIN7 when used with non-administrative account. UI is not saving accounts, click on "synchronize clock" starts endless loop and online upgrades can break installation and result with errors like upper one. |
|
|
|
Core updated, confirmed update of UI. Syncing was bad and after core restart suddenly stopped working. Tried temporary version and got same errors: EDIt: better explanation |
|
|
|
how to check rig speed? randomly speed 0 h\s and need restart rig for work
+1 |
|
|
|
Me:  |
|
|
|
I think I might setup a few publicly accessible nodes, but they obviously don't allow you to mint...
I think I might setup a service to host private minting VMs for people. That sounds like something that is a good plan...
Also you can purchase a raspberry pi 4, and we can provide you an image for it with our custom Qortal Kernel, that runs AMAZINGLY.
Any ARM device in theory can work, and we plan to build a bunch of custom ARM kernels.
I have couple of different Orange PIs, so instructions for building will for sure help spreading nodes much faster than waiting for specific custom kernels. |
|
|
|
In theory, if I have configured the public node network correctly, old versions of The Qortal Core, will update upon reaching the update-approval block (meaning, the block that the dev team ((with 20% agreement betwixt them)) decided to 'approve' the transaction, thus making it a permanent portion of the chain, and setting a block by which updates will take place upon any node synchronizing as far.
Essentially - IF YOU'RE ON AN OLD VERSION, IT WILL AUTO-UPDATE IF MY NETWORK IS SETUP CORRECTLY.
Running qortal-1.2.2 now on 64-bit WIN7 and CPU usage is still over 50% on old i3 laptop. Because I'm not running anything with administrative privileges, real loop show starts when right clicked on qortal taskbar icon and start Synchronize clock. Don't do this at home... |
|
|
|
Install Qortal Core + UI, have your QORA address seed ready, launch the run.sh (GNU/Linux) or run.bat (Windoze) Script to start the core, run the UI, choose "Login", then "QORA Address Seed", enter your seed, done.  I did it in Windows and got constant >50% CPU usage by Qortal.exe. What's the catch? |
|
|
|
It has been announced since last year, I think it was summer 2019 when it was being discussed how to go about the burn process.
You claim that burn deadline was announced since last year? No. It was announced 4 DAYS before happening. |
|
|
|
The original deadline was 1 Jan 2020, so to be fair the dev gave the Qora community a 5 month extension for the coin burn.
Oh, I see. Original was 1 Jan. So 6 Jun is fake one. That's why it was announced astonishing 4 days before. |
|
|
|
This leads me to the reason I came here to post today... QORA FINAL BURN DATE - JUNE 6, 2020
We realize that we have changed the date a few times, but that was only because people had pushed me to set a launch date when I didn't really want to, as I knew that it probably wouldn't be exact... as this is how totally new prototype development goes...
Regardless, I set dates (that were missed)...
Great timing. Announcement unbelievable 4 days before deadline. You could do it better announcing it 4 hours or 4 minutes before. Respect. |
|
|
|
I assume You have at least 4 doors, so You can use all of them as door stoppers...  |
|
|
|
my issue they made a lot of ASIC equipment (but no more for SC) and they made a lot of coins, as a result, to speculate with...but the supposed purpose of
Siacoin as a decentralized anonymous file server worldwide storage network is way, way behind and just plain silly for cost/use, etc in its present form.
I still think Sia-Tech is gonna pull a ButterFly Labs in the USA and just walk with Bankruptcy. I don't see how they can pull off their 'supposed' network after losing
money on the GRIN hardware and other dubious stuff.
I'd like to be proven wrong on the storage coming up to speed..but just don't see any talk or any action as such at the same level as speculation hype on Siacoin prices
and difficulty nor on the movement of hardware for SC coin ASIC'S...and supposedly that was the whole purpose of SC coin but it has been lost in the dogpile.
What is Your problem with SIA decentralized storage? Do You want to sell or buy storage? |
|
|
|
Add to the build options? Tried that first with no success. THX anyhow. |
|
|
|
Hello, I have stoped my 2 BKX for 2 month. This morning I put them on but there is no activity. (No device running, no pools loaded).  Pools are good setup. I can ping any server from Baikal, no IP problem. Thank you Make and export backup. Flash uSD card with newest firmware. Restore backup. 99% it will be solved, because You will also reconnect OrangePC during procedure. |
|
|
|
As BK-X10 became non-profitable, I started tinkering with them. But, with latest baikalminer image (2.2) I can't compile sgminer from cod3gen github. Reporting problem with libraries: CCLD sgminer
/usr/bin/ld: submodules/libusb-bk/libusb/.libs/libusb-1.0.a(libusb_1_0_la-core.o): relocation R_ARM_THM_MOVW_ABS_NC against `a local symbol' can not be used when making a shared object; recompile with -fPIC
submodules/libusb-bk/libusb/.libs/libusb-1.0.a: error adding symbols: Bad value
collect2: error: ld returned 1 exit status
Makefile:912: recipe for target 'sgminer' failed
make[2]: *** [sgminer] Error 1
make[2]: Leaving directory '/home/baikal/sgminer-baikal'
Makefile:1824: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/baikal/sgminer-baikal'
Makefile:717: recipe for target 'all' failed
make: *** [all] Error 2
Helping hand anyone? |
|
|
|
Willing to donate a few $$ (up to $100) in crypto to someone who can post results on Grin (Cuck31) on AMD R9 Nitro Fury 8GB HBM (or other Fury R9 card with 8GB HBM) with card optimized for low power usage.
Good luck finding Fury with 8GB. AFAIK 4GB is what You can find. |
|
|
|
... and You can have 4-5% discount on Aliexpress registering with my signature referral link. Not bad.  |
|
|
|
|
Show Posts
