Here's a Mac build of the Qt wallet with the latest code. The dev has upped the version number, so it's at a new URL: https://www.dropbox.com/s/qe1klcgo64bolxr/Slimcoin-Qt-0.3.1.0-Mac.zipAll the same caveats everybody's discussing apply. You'll need to delete your blk* files in ~/Library/Application Support/SLIMcoin and resync, and you may have trouble syncing. All the fixes that have been discussed apply as well. |
|
|
|
UPDATES: - Updated BitNote wallet to latest version.
- Added wallet for "new" Piggycoin (relaunched X11 version)
- Updated Digitalcoin to latest version.
- Updated Donationcoin to latest version.
- Continuing to update the Slimcoin wallet as the dev releases fixes, but since the version number hasn't changed, the URL hasn't changed.
|
|
|
|
(Moved from the other Blade support thread) Has anyone successfully replaced the fan on their Gridseed Blade with a quieter one? I did a bit of research, and the fan on the Blade seems to be a YY9225M12 ( http://snowfancomcn.ztouch-make-hn-16221.shushang-z.cn/products_detail/&productId=225.html) which pushes about 90 CFM and operates at about 45dbA. The only 92mm alternatives I was able to find were some of the higher-power Delta fans and the Vantec Tornado, both of which operate at 90+ CFM, but also at 50-55dbA. Of course, the question is whether the Blade really needs 90 CFM or whether Gridseed was just playing it safe. There are quieter fans at 80 CFM and much quieter fans at 43 CFM. And a few people have mentioned using a Noctua NF-B9, which is only about 31 CFM, but nobody's actually posted about whether the Noctua ran the Blade stably for any long period of time. Anyway, if anyone's managed to quiet the Blade down without melting it, please post! I still have fans on my 5 chips and they are way louder. I think the fan size and the length of the connector cable (connector should match obviously) all need to worry about. I put copper heatsinks ($4.00) and an old P4 fan (free) blowing down across the sets of heatsinks and "hot" areas of the cards (backside of the pcb) http://postimg.org/image/lh45dergt/I ran a copper wire through the holes to make long legs, one is stuck in contact putty (for posters), the fan is taped at the back with aluminum tape. It won't easily come off. This did not help with HW errors, i still have one that gets a few each day compared to the other that maybe has one (pool switching causes more with them). I made some labels for my gridseeds. I had to use one blank one though, http://postimg.org/image/hc3rbn931/ forgive the dust. The only mod that might quiet them down (bigger fan!)... in the mod section search for Gridseed Blade Widebody. Thanks for all the information! Yeah, maybe I have a particularly noisy fan--it's not as loud as the 5-chip fans but it has a really annoying whine. Your setup is pretty sweet. How did you attach the heatsinks? Just the stock adhesive, or anything special? As far as the second fan goes, I wonder if it would work to position the blades horizontally and blow air across with one of these fans: http://amzn.com/B00080G0BK - I guess that would be kind of like what you've done, though the Pentium fan is probably a lot faster. Thanks for the pointer to the widebody mod, too. Gonna check that out. |
|
|
|
(Moved from the other Blade support thread) Has anyone successfully replaced the fan on their Gridseed Blade with a quieter one? I did a bit of research, and the fan on the Blade seems to be a YY9225M12 ( http://snowfancomcn.ztouch-make-hn-16221.shushang-z.cn/products_detail/&productId=225.html) which pushes about 90 CFM and operates at about 45dbA. The only 92mm alternatives I was able to find were some of the higher-power Delta fans and the Vantec Tornado, both of which operate at 90+ CFM, but also at 50-55dbA. Of course, the question is whether the Blade really needs 90 CFM or whether Gridseed was just playing it safe. There are quieter fans at 80 CFM and much quieter fans at 43 CFM. And a few people have mentioned using a Noctua NF-B9, which is only about 31 CFM, but nobody's actually posted about whether the Noctua ran the Blade stably for any long period of time. Anyway, if anyone's managed to quiet the Blade down without melting it, please post! |
|
|
|
could you please explain what will happen if i burn 1 coin? or 0.1?
Great explanation from earlier in the thread: - PoB is the same as mining contracts! This is great, because every miner doing PoB has the same probability of hitting PoB blocks. Further burning coins is like extending your mining contract, not contracting more hashing power.
- You can know how much of your burnt coins has been used to hash on PoB via the decay feature. Decay/Confirmed Burnt coins = Percentage done of the "mining contract".
No its not. The more coins you burn the more chance of hitting a PoB block. If you burn only 10 coins chances you find a PoB block are almost none. Don't fucking spread misinformation. You're right. From the whitepaper: "The more coins that are burnt, the smaller this unique burn hash will be, making it more likely to be valid and accepted by the network." Gonna go back and edit my post. |
|
|
|
could you please explain what will happen if i burn 1 coin? or 0.1?
Great explanation from earlier in the thread: - PoB is the same as mining contracts! This is great, because every miner doing PoB has the same probability of hitting PoB blocks. Further burning coins is like extending your mining contract, not contracting more hashing power.
- You can know how much of your burnt coins has been used to hash on PoB via the decay feature. Decay/Confirmed Burnt coins = Percentage done of the "mining contract".
From reading the dev's whitepaper, it seems like the more coins you burn, the higher your chance of hitting a PoB block. Otherwise this explanation seems accurate, though. |
|
|
|
There's a bug or something. For example, I received a PoB block. In transactions, it shows (amount) 10.74. But if I click details, it says: +0.202502 SLM
Happened to me 3 times already. Is it a visual bug, or I'm not receiving all the coins I should?
Lol same somehow got 2 burn blocks like this. Oddly though the wallet that mined em was shutdown at the time!!! on sync this morning 2 pob's between pool payments im quite confused as i thought the wallet had to be running for pob  I noticed a few days ago that if you send coins from a PoB block from one wallet to another, they show up with the burn icon in the UI. So maybe the pool generated a couple of PoB blocks and split them among the pool miners. I received a couple of blocks like that at as well, at an address I've only used for pool mining. |
|
|
|
Can't build with boost 1.55 .Tried on Ubuntu 14.04 and Debian 7 obj/db.o: In function `operator/':
/usr/local/include/boost/filesystem/path.hpp:648: undefined reference to `boost::filesystem::path::operator/=(boost::filesystem::path const&)'
obj/db.o: In function `create_directory':
/usr/local/include/boost/filesystem/operations.hpp:405: undefined reference to `boost::filesystem::detail::create_directory(boost::filesystem::path const&, boost::system::error_
code*)'
obj/db.o: In function `operator/':
/usr/local/include/boost/filesystem/path.hpp:648: undefined reference to `boost::filesystem::path::operator/=(boost::filesystem::path const&)'
obj/db.o: In function `sleep':
/usr/local/include/boost/thread/pthread/thread_data.hpp:249: undefined reference to `boost::this_thread::hiden::sleep_until(timespec const&)'
obj/init.o: In function `remove':
/usr/local/include/boost/filesystem/operations.hpp:496: undefined reference to `boost::filesystem::detail::remove(boost::filesystem::path const&, boost::system::error_code*)'
obj/init.o: In function `is_directory':
/usr/local/include/boost/filesystem/operations.hpp:294: undefined reference to `boost::filesystem::detail::status(boost::filesystem::path const&, boost::system::error_code*)'
obj/init.o: In function `operator/':
/usr/local/include/boost/filesystem/path.hpp:648: undefined reference to `boost::filesystem::path::operator/=(boost::filesystem::path const&)'
obj/init.o: In function `sleep':
/usr/local/include/boost/thread/pthread/thread_data.hpp:249: undefined reference to `boost::this_thread::hiden::sleep_until(timespec const&)'
obj/main.o: In function `space':
/usr/local/include/boost/filesystem/operations.hpp:520: undefined reference to `boost::filesystem::detail::space(boost::filesystem::path const&, boost::system::error_code*)'
obj/main.o: In function `operator/':
/usr/local/include/boost/filesystem/path.hpp:648: undefined reference to `boost::filesystem::path::operator/=(boost::filesystem::path const&)'
obj/main.o: In function `boost::thread::start_thread()':
/usr/local/include/boost/thread/detail/thread.hpp:180: undefined reference to `boost::thread::start_thread_noexcept()'
obj/bitcoinrpc.o: In function `sleep':
/usr/local/include/boost/thread/pthread/thread_data.hpp:249: undefined reference to `boost::this_thread::hiden::sleep_until(timespec const&)'
obj/bitcoinrpc.o: In function `boost::thread::start_thread()':
/usr/local/include/boost/thread/detail/thread.hpp:180: undefined reference to `boost::thread::start_thread_noexcept()'
obj/bitcoinrpc.o: In function `boost::thread::do_try_join_until(timespec const&)':
/usr/local/include/boost/thread/detail/thread.hpp:768: undefined reference to `boost::thread::do_try_join_until_noexcept(timespec const&, bool&)'
obj/bitcoinrpc.o: In function `boost::filesystem::path::has_root_directory() const':
/usr/local/include/boost/filesystem/path.hpp:444: undefined reference to `boost::filesystem::path::root_directory() const'
obj/bitcoinrpc.o: In function `boost::filesystem::operator/(boost::filesystem::path const&, boost::filesystem::path const&)':
/usr/local/include/boost/filesystem/path.hpp:648: undefined reference to `boost::filesystem::path::operator/=(boost::filesystem::path const&)'
obj/bitcoinrpc.o: In function `boost::filesystem::exists(boost::filesystem::path const&)':
/usr/local/include/boost/filesystem/operations.hpp:289: undefined reference to `boost::filesystem::detail::status(boost::filesystem::path const&, boost::system::error_code*)'
obj/bitcoinrpc.o: In function `call_once<void (*)()>':
/usr/local/include/boost/thread/pthread/once_atomic.hpp:145: undefined reference to `boost::thread_detail::enter_once_region(boost::once_flag&)'
/usr/local/include/boost/thread/pthread/once_atomic.hpp:157: undefined reference to `boost::thread_detail::commit_once_region(boost::once_flag&)'
/usr/local/include/boost/thread/pthread/once_atomic.hpp:153: undefined reference to `boost::thread_detail::rollback_once_region(boost::once_flag&)'
/usr/local/include/boost/thread/pthread/once_atomic.hpp:145: undefined reference to `boost::thread_detail::enter_once_region(boost::once_flag&)'
/usr/local/include/boost/thread/pthread/once_atomic.hpp:157: undefined reference to `boost::thread_detail::commit_once_region(boost::once_flag&)'
/usr/local/include/boost/thread/pthread/once_atomic.hpp:153: undefined reference to `boost::thread_detail::rollback_once_region(boost::once_flag&)'
obj/util.o: In function `operator/':
/usr/local/include/boost/filesystem/path.hpp:648: undefined reference to `boost::filesystem::path::operator/=(boost::filesystem::path const&)'
I had to build the Mac version against Boost 1.49. Maybe the same is true for Linux. |
|
|
|
Don't seem to be able to get it to work on windows localhost even with the daemon running.
rpcport=41683 ??
rpcallowip=127.0.0.1
Can anyone confirm that finding blocks with slimminer works? I have set up like the OP told but never find any block (one PC with daemon as host and 20 machines with slimminer as client. slimminer shows hashrate in every computer. solomining with 90khs for 2 days and can't even find one block.) I change to solomine with the daemon only (with gen=0) and only 3 machines (around 12khs in total). Found 5 blocks in 2 days already. Somethings certainly not right there then. I've only being mining with the wallet thus far - apart from a few hours test in the temporary pool. Again, I did see accepted shares with the slimminer in the temporary pool. ~ Are you mining via linux machines only ? Yeah I'm mining with the daemon, technically. My shares in the temporary pool get accepted too, but the daemon never accepts slimminer shares even from the same machine. I'm using linux in all machines. I've seen this too, between two Linux machines, one running the daemon and one running slimminer. Looking at the output of "netstat -a", each machine ends up with a bunch of connections to the other machine in the TIME_WAIT state. So I wonder if something's wrong with the RPC listener. The tricky part is that neither side shows an error message, and slimminer looks like it's mining, but of course there's no traffic going over those TIME_WAIT connections. |
|
|
|
Looks like the network hashrate dropped significantly, but the difficulty is still high. |
|
|
|
I found two blocks today with 1 miner i7 4770
2 small blocks, so i think they are both PoW (10.77 and 13.38)
When a PoB block is found, how does it look like?
If you're using the Qt wallet, a PoB block will show up on the home screen with a different icon than a PoW block. I haven't figured out how to tell from RPC, though. |
|
|
|
UPDATES: - Replaced wwwcoin wallet with W2Coin wallet.
- Replaced Bitnote wallet with relaunched (X11) Bitnote wallet.
- New Trollcoin wallet.
- Updated Slimcoin wallet (URL did not change).
|
|
|
|
Been mining this since minute 0, here are my two uSLIMs: - PoW is pretty difficult because there's only solo mining currently. With around 2.5 KH/s you get roughly 1 block daily. That's pretty good considering network hash has been steadily rising.
- PoB is the same as mining contracts! This is great, because every miner doing PoB has the same probability of hitting PoB blocks. Further burning coins is like extending your mining contract, not contracting more hashing power.
- You can know how much of your burnt coins has been used to hash on PoB via the decay feature. Decay/Confirmed Burnt coins = Percentage done of the "mining contract".
- DCrypt is nice and all, but i don't see it as a very ASIC resistant hash. If PoW will be enabled on later phases (as it should be) there will be definitively interest on creating ASICs because the coin will be VERY scarce due to burn rates.
- I'm liking the order book in exarena, a push to get this listed on http://sharexcoin.com would be great.
- Thread dwellers beware: Feeding trolls is against your best interest. Don't feed the trolls http://www.zoomnews.es/sites/default/files/images/old/dont_feed_the_troll.jpg
This is a great explanation of PoB. Thank you! |
|
|
|
The blockchain is just under 500 MB.
There's also some internal overhead from the database code, so that could be it. I assume your friend has restarted the wallet, right? Also, your friend can see how much memory Florincoin is using and how much overall memory is used on the system with the Activity Monitor app in /Applications/Utilities. |
|
|
|
The blockchain is just under 500 MB.
There's also some internal overhead from the database code, so that could be it. I assume your friend has restarted the wallet, right? |
|
|
|
|
Show Posts
