Search content
Sort by
Showing 20 of 41 results by Wildvest
Re: [ANN][BCC] Bitconnect Coin - Decentralized Cryptocurrency
Re: [ANN] [CHC] ChainCoin - 0.9.2.4 Update - Cryptopia & Novaexchange
soon there will be a new release with new reward structure
there is already a BETA release available - https://github.com/chaincoin/chaincoin/releases/
there is already a BETA release available - https://github.com/chaincoin/chaincoin/releases/
Re: [ANN] [CHC] ChainCoin - 0.9.2.3 Update - Affordable MasterNodes - Cryptopia
if somebody care, my adapted & tested chaincoind daemon start script with autostart for the standard Masternode Setup on Ubuntu 16.04 (and higher)
copy text into a new file /etc/systemd/system/chaincoind.service
run
reload config
or better reboot and check for startup with
advantage is its autostart on reboot and also on daemon crash
copy text into a new file /etc/systemd/system/chaincoind.service
Code:
[Unit]
Description=chaincoin's distributed currency daemon
After=network.target
[Service]
User=root
Group=root
Type=forking
PIDFile=/root/.chaincoin/chaincoind.pid
ExecStart=/usr/local/bin/chaincoind -daemon -pid=/root/.chaincoin/chaincoind.pid -conf=/root/.chaincoin/chaincoin.conf -datadir=/root/.chaincoin
#-disablewallet
Restart=always
PrivateTmp=true
TimeoutStopSec=60s
TimeoutStartSec=2s
StartLimitInterval=120s
StartLimitBurst=5
[Install]
WantedBy=multi-user.target
Description=chaincoin's distributed currency daemon
After=network.target
[Service]
User=root
Group=root
Type=forking
PIDFile=/root/.chaincoin/chaincoind.pid
ExecStart=/usr/local/bin/chaincoind -daemon -pid=/root/.chaincoin/chaincoind.pid -conf=/root/.chaincoin/chaincoin.conf -datadir=/root/.chaincoin
#-disablewallet
Restart=always
PrivateTmp=true
TimeoutStopSec=60s
TimeoutStartSec=2s
StartLimitInterval=120s
StartLimitBurst=5
[Install]
WantedBy=multi-user.target
run
Code:
systemctl reenable chaincoind
reload config
Code:
systemctl daemon-reload
systemctl restart chaincoind
systemctl restart chaincoind
or better reboot and check for startup with
Code:
systemctl status chaincoind
advantage is its autostart on reboot and also on daemon crash
Re: [ANN][CRW] CROWN (SHA256) | Core Updates | Thrones | Merge Mining
NICE ! looking forward
A short status update on the iOS version of CrownPay. It's progressing nicely. All basic features are working and we hope to start beta testing soon.
Re: [ANN][CRW] CROWN (SHA256) | Experimental Commodity | Trons | Merge Mining
Thanks for the info, chaositec (meanwhile enjoying the faster throne rewards)
Number of thrones will dip for a few hours, then go back up
Re: [ANN][CRW] CROWN (SHA256) | Core Updates | Thrones | Merge Mining
nice video ! Thanks
Hey guys!
I made a new video about cryptocurrencies using a masternode system.
Since Crown has this system, I talk about it too!
https://www.youtube.com/watch?v=ZRHftvRY6XI
I think any form of marketing is welcome, right?
Congrats on hitting 10M+ market cap!
I made a new video about cryptocurrencies using a masternode system.
Since Crown has this system, I talk about it too!
https://www.youtube.com/watch?v=ZRHftvRY6XI
I think any form of marketing is welcome, right?
Congrats on hitting 10M+ market cap!
Re: [ANN][CRW] CROWN (SHA256) | Core Updates | Thrones | Merge Mining
GREAT news ! Thanks for the update
CROWN Update 8.4.2014
Core team meeting in Prague 27 and 28th of April 2017
After the December 2016 meeting in london, 6 members of the Core dev team are meeting in Prague, several of which are flying across the Atlantic ocean. Urban_idler, stonehedge, chaositec, defunctec, infernoman, crowncoin_knight will be meeting on the 27th and 28th of April do discuss next steps which will lead CROWN toward our goal: Crown Revolution
Open session for the Crown community
The dev team will hold an open session for anybody who wants to meet the team and discuss Crown on the 29th of Aprll starting at 10:00. Please follow BTC talk for further details. We will put an update on the the place of the meeting.
Next code release in May 2017
The team plans another release which include the following features. One of the most important updates will be enabling our Throne voting mechanism on Crown. We are currently working on:
DNS NODES
InstantX implementation
fix alerts
fix sporks
throne output ADDR
disable ipv6 thrones (only 20% of the internet is capable of handling ipv6 less in smaller countries)
stronger enforcement on local address nodes (127.0.0.1)
enable timestamping directly in the QT
throne enforcement
superblock enforcement
superblocks
New API, Throne growth and crowncentral.net launch
Nodes on the Crown Network are currently called Thrones and just sit there. After the May code update, we expect to be testing an API intended to enable the construction of an application layer of the network connecting through the network nodes. So after the May update the nodes will start to become active, and we will be exclusively referring to them as TRONs. This has been an understandable point of confusion for many.
We will also be discussing a reduction of the collateral required to operate a Tron. Specifically, the proposal would be to set the collateral amount to 5,000 CRW in the May update.
The total number of Thrones / Trons grew to a new record of 750 earlier, which means over 2 million dollars in locked value. It also demonstrates the willingness of new investors to hold CROWN long term as ROI is attractive.
Additionally, one of our community members has launched his complex Throne monitoring app at www.crowncentral.net where you can check your Throne ROI as well as.
We are very excited about the recent growth of the CROWN community and we will be posting a detailed update after our Prague meeting.
The Core Dev team
CROWN Update 8.4.2014
Core team meeting in Prague 27 and 28th of April 2017
After the December 2016 meeting in london, 6 members of the Core dev team are meeting in Prague, several of which are flying across the Atlantic ocean. Urban_idler, stonehedge, chaositec, defunctec, infernoman, crowncoin_knight will be meeting on the 27th and 28th of April do discuss next steps which will lead CROWN toward our goal: Crown Revolution
Open session for the Crown community
The dev team will hold an open session for anybody who wants to meet the team and discuss Crown on the 29th of Aprll starting at 10:00. Please follow BTC talk for further details. We will put an update on the the place of the meeting.
Next code release in May 2017
The team plans another release which include the following features. One of the most important updates will be enabling our Throne voting mechanism on Crown. We are currently working on:
DNS NODES
InstantX implementation
fix alerts
fix sporks
throne output ADDR
disable ipv6 thrones (only 20% of the internet is capable of handling ipv6 less in smaller countries)
stronger enforcement on local address nodes (127.0.0.1)
enable timestamping directly in the QT
throne enforcement
superblock enforcement
superblocks
New API, Throne growth and crowncentral.net launch
Nodes on the Crown Network are currently called Thrones and just sit there. After the May code update, we expect to be testing an API intended to enable the construction of an application layer of the network connecting through the network nodes. So after the May update the nodes will start to become active, and we will be exclusively referring to them as TRONs. This has been an understandable point of confusion for many.
We will also be discussing a reduction of the collateral required to operate a Tron. Specifically, the proposal would be to set the collateral amount to 5,000 CRW in the May update.
The total number of Thrones / Trons grew to a new record of 750 earlier, which means over 2 million dollars in locked value. It also demonstrates the willingness of new investors to hold CROWN long term as ROI is attractive.
Additionally, one of our community members has launched his complex Throne monitoring app at www.crowncentral.net where you can check your Throne ROI as well as.
We are very excited about the recent growth of the CROWN community and we will be posting a detailed update after our Prague meeting.
The Core Dev team
Re: [ANN][CRW] CROWN (SHA256) | Core Updates | Thrones | Merge Mining
very nice indeed ! Thanks for you awesome work !
After many months of tweaking Iquidus, my block explorer is finally ready for use.
http://ex.crownlab.eu/
Blocks are updated every 60 seconds.
The movement tab shows transactions above 5,000 CRW. 1k transactions are highlighted in orange...very useful for tracking Thrones as they are set up. Transactions over 100k are shown in red.
Enjoy.
http://ex.crownlab.eu/
Blocks are updated every 60 seconds.
The movement tab shows transactions above 5,000 CRW. 1k transactions are highlighted in orange...very useful for tracking Thrones as they are set up. Transactions over 100k are shown in red.
Enjoy.
Re: [ANN][CRW] CROWN (SHA256) | Core Updates | Thrones | Merge Mining
if somebody care, my adapted & tested crownd daemon start script with autostart for the standard Throne (Tron) Setup on Ubuntu 16.04 (and higher)
copy text into a new file /etc/systemd/system/crownd.service
run
reload config
or better reboot and check for startup with
advantage is its autostart on reboot and also on daemon crash
copy text into a new file /etc/systemd/system/crownd.service
Code:
[Unit]
Description=Crown's distributed currency daemon
After=network.target
[Service]
User=root
Group=root
Type=forking
PIDFile=/root/.crown/crownd.pid
ExecStart=/usr/local/bin/crownd -daemon -pid=/root/.crown/crownd.pid -conf=/root/.crown/crown.conf -datadir=/root/.crown
#-disablewallet
Restart=always
PrivateTmp=true
TimeoutStopSec=60s
TimeoutStartSec=2s
StartLimitInterval=120s
StartLimitBurst=5
[Install]
WantedBy=multi-user.target
Description=Crown's distributed currency daemon
After=network.target
[Service]
User=root
Group=root
Type=forking
PIDFile=/root/.crown/crownd.pid
ExecStart=/usr/local/bin/crownd -daemon -pid=/root/.crown/crownd.pid -conf=/root/.crown/crown.conf -datadir=/root/.crown
#-disablewallet
Restart=always
PrivateTmp=true
TimeoutStopSec=60s
TimeoutStartSec=2s
StartLimitInterval=120s
StartLimitBurst=5
[Install]
WantedBy=multi-user.target
run
Code:
systemctl reenable crownd
reload config
Code:
systemctl daemon-reload
systemctl restart crownd
systemctl restart crownd
or better reboot and check for startup with
Code:
systemctl status crownd
advantage is its autostart on reboot and also on daemon crash
Re: [ANN][CRW] CROWN (SHA256) | Core Updates | Thrones | Merge Mining
After some notifications from users in germany and another in malaysia, we've decided to bring online a few more DNS nodes as well as electrumx nodes. Currently online is quebec, singapore, bangalore, and frankfurt. Since most of our users haven't had any issues im trying to focus on some spots of the earth that may not be covered as greatly.
awesome ! reaction time of the CROWN team is great, even on weekends, sync is going great again ! Thanks to the team
Re: [ANN][CRW] CROWN (SHA256) | Core Updates | Thrones | Merge Mining
more dumping incoming...
GREAT ! i can load up CRW at a bargain - amazing
Re: Is anyone able to replicate this guys 6990 results of 432-455Mh/s per GPU??
The last couple of days I've been tweaking trying to get the highest Mh/s I can on my 6990 and after trying a number of different overclock settings, extra flags, every kernel tweak I could find and even several different miners and pools I still don't get anywhere near the 432-455Mh/s at 910Mhz that this guy is showing he's able to achieve here:
http://forum.bitcoin.org/index.php?topic=25798.0
So I'm just wondering what it is I'm missing that he found in order to get that additional ~27-50Mh/s at only 910Mhz core speed. Is anyone else here able to replicate his Mh/s or anywhere close to it?
I'm using the exact same settings as him and this is what I'm getting at 910Mhz core clock per GPU:
Operating System:
Windows 7 X64
Aero Theme Disabled
Drivers:
11.7 preview
Software:
GUIminer: Miner(Phoenix with 3% patch to phat kernal), Flags(-k phatk VECTORS BFI_INT AGGRESSION=7 WORKSIZE=128)
GPU Clocks:
Core: 910
Mem: 840
Cooling:
60% Fan speed on cards
Temps:
Hottest: 72c
Coolest: 71c
Hash Rate:
405 MH/s per GPU
http://forum.bitcoin.org/index.php?topic=25798.0
So I'm just wondering what it is I'm missing that he found in order to get that additional ~27-50Mh/s at only 910Mhz core speed. Is anyone else here able to replicate his Mh/s or anywhere close to it?
I'm using the exact same settings as him and this is what I'm getting at 910Mhz core clock per GPU:
Operating System:
Windows 7 X64
Aero Theme Disabled
Drivers:
11.7 preview
Software:
GUIminer: Miner(Phoenix with 3% patch to phat kernal), Flags(-k phatk VECTORS BFI_INT AGGRESSION=7 WORKSIZE=128)
GPU Clocks:
Core: 910
Mem: 840
Cooling:
60% Fan speed on cards
Temps:
Hottest: 72c
Coolest: 71c
Hash Rate:
405 MH/s per GPU
i have about the same results like you - on linux - catalyst 11.4 - sdk 2.4 - poclbm (phatk)
Re: further improved phatk OpenCL Kernel (> 2% increase) for Phoenix - 2011-07-06
THANKS for your efforts ! just reporting back 
6990 version 2011-07-06 with Catalyst 11.4, SDK 2.4 now equal with the latest poclbm (phatk) - maybe 0.5 MH/s slower
6990 version 2011-07-06 with Catalyst 11.4, SDK 2.4 now equal with the latest poclbm (phatk) - maybe 0.5 MH/s slower
Re: LinuxCoin A lightweight Debian based OS with everything ready to go.
maybe useful: http://fnoose.com/bitcoin/arbitrage/?MhpJ=2&USDpkWh=0.20 
i'm running 12 x 6990 at the absolute edge in overclocking mode (power, temp) - they are all running at 100% 24/7 - unfortunately i have to clock down if the ambient temp is rising, but i use a script for that - a few pic: http://imgur.com/a/usqDL
I love this pic http://i.imgur.com/fevHc.jpg
Would you care to share your script(s) or how you show temperatures and the last picture where it shows V (is that volts?)?
sorry for the OT
the bash script for the autom. clock control (based on temp) is from the forum here, but i don't have the thread in mind, you may try the forum search function
the lower terminal windows are the output of lm-sensors (took me 2 days to fix all the kernel and driver stuff :-( ) - important for me is that temp sensor, it give me some estimate about the ambient (server room) temperature - the A/C is a old lady already
the V - yes that are Volts, since there is nowhere a hwmon for the 12V, i use the 3.3 V reference as a guessing - in idle it is around 3.3, below 3.10 the motherboard or the cards crashing frequently, so it is a good guess ;-)