Search content
Sort by
Showing 20 of 147 results by celkaris
Re: 🔥[ANN][ICO] Welltrado — Global Blockchain-Backed Loans Marketplace🔥
I feel that this project is very good, and I'm looking forward
to the next step of the team, I will continue to pay attention
to this project, hope that the team also make unremitting efforts,
earnestly planning and implementation, team refueling!
to the next step of the team, I will continue to pay attention
to this project, hope that the team also make unremitting efforts,
earnestly planning and implementation, team refueling!
there's also an "ARCTIC COOLING BREEZE Pro" 92mm, with variable speed and 4 usb ports. It's usb-powered though, so those 4 ports will probably only accept low-power devices, and no block erupter.
It can be found at 12 EUR per unit in public and online stores here.
I'll probably look into this one, cause i'm actually using a way too big fan to cool my 5 block erupters, wasting energy.
(i for sure won't go fanless with block erupters, they really gets way too hot in a few minutes, if no fan is used).
It can be found at 12 EUR per unit in public and online stores here.
I'll probably look into this one, cause i'm actually using a way too big fan to cool my 5 block erupters, wasting energy.
(i for sure won't go fanless with block erupters, they really gets way too hot in a few minutes, if no fan is used).
Re: TRC: 32-bit Linux client cannot synchronize with TerraCoin network
Bug still present and cause is unknown, but it is "fixed" by https://github.com/terracoin/terracoin/commit/856387e
Was this fix tested? When I check the code, I don't understand it... Is the function GetEmaNextWorkRequired right place for the fix??
Well, it is not a fix but workaround. It is working, blockchain was synchronized till block 190965.
Exactly. This commit allowing affected machines to synchronize w/o any trouble, it also adds additional checkpoint right after "messy" block 137161 to make sure that you are in proper chain.This is only workaround, not real fix and it is valid only for this block.
If this unknown bug hit again code need be changed again, and again...
except that the EMA thing is not in use anymore, so there's (hopefully) no need to change it again.
i've no time to spend on that, but i'd like to see what previous block somehow borked the ema calculation in the ~2k (?) blocks prior to 137161, and how
I like the alert related changes bring by this release though. I guess alerts will be used to announce the (HOPEFULLY) next major change announced on github issue tracker (shorter retarget window with smaller caps), so the coin returns to a faster block rate.
FYI, new email received from trc mailing list this morning :
Quote
Re: [Terracoin-announce] terracoin update 0.1.3-36
From: TerraCoin - 2013-04-15 12:51
Terracoin update 0.1.3-36 is now available for download at our
sourceforge and github repositories.
This build addresses some issues in the difficulty adjustment algorithm,
recently revealed by the massive adoption on the live blockchain.
The detailed change log will be published here once the patch is fully
applied on the network, here is a summary :
- overall network difficulty will respond slightly slower to big
variations in hashrate power
- averaged data used to compute targets will now be capped and adjusted
symmetrically, lowering the effect of malformed/erroneous inputs
- target will be capped in a symmetrical way
Once fully deployed, this build will provide more resilience to hashing
spikes and narrow down the difficulty variations.
Due to the impacted features, this build will be *MANDATORY* on block
_110322_.
This should occur in 2.5 to 6 days from now.
Sorry for the 3 mandatory updates in a row, the huge hashing variations
have to be contained so the whole blocks generation rate gets close to a
sane value.
Again, the full, detailed changelog will be exposed here once users
upgraded.
Links:
------
source:
master branch at https://github.com/terracoin/terracoin
Windows binaries:
http://sourceforge.net/projects/terracoin/files/SatoshiClone/terracoin-0.1.3-36-win32.zip/download
Source-based update:
--------------------
If you previously cloned our repository, you may update using:
cd /path/to/your/local/clone/
git checkout master # locally on the master branch locally
git pull origin master # fetches and merges remote master branch
# headless daemon:
cd src
nice make -f makefile.unix -j 4
# qt-client:
qmake USE_IPV6=-
nice make -j 4
Update confirmation emails from exchanges services, mining pools and
wallets would be greatly appreciated.
Thanks by advance.
regards,
TRC.
--
TRC.
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
Terracoin-announce mailing list
Terracoin-announce@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/terracoin-announce
From: TerraCoin - 2013-04-15 12:51
Terracoin update 0.1.3-36 is now available for download at our
sourceforge and github repositories.
This build addresses some issues in the difficulty adjustment algorithm,
recently revealed by the massive adoption on the live blockchain.
The detailed change log will be published here once the patch is fully
applied on the network, here is a summary :
- overall network difficulty will respond slightly slower to big
variations in hashrate power
- averaged data used to compute targets will now be capped and adjusted
symmetrically, lowering the effect of malformed/erroneous inputs
- target will be capped in a symmetrical way
Once fully deployed, this build will provide more resilience to hashing
spikes and narrow down the difficulty variations.
Due to the impacted features, this build will be *MANDATORY* on block
_110322_.
This should occur in 2.5 to 6 days from now.
Sorry for the 3 mandatory updates in a row, the huge hashing variations
have to be contained so the whole blocks generation rate gets close to a
sane value.
Again, the full, detailed changelog will be exposed here once users
upgraded.
Links:
------
source:
master branch at https://github.com/terracoin/terracoin
Windows binaries:
http://sourceforge.net/projects/terracoin/files/SatoshiClone/terracoin-0.1.3-36-win32.zip/download
Source-based update:
--------------------
If you previously cloned our repository, you may update using:
cd /path/to/your/local/clone/
git checkout master # locally on the master branch locally
git pull origin master # fetches and merges remote master branch
# headless daemon:
cd src
nice make -f makefile.unix -j 4
# qt-client:
qmake USE_IPV6=-
nice make -j 4
Update confirmation emails from exchanges services, mining pools and
wallets would be greatly appreciated.
Thanks by advance.
regards,
TRC.
--
TRC.
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
Terracoin-announce mailing list
Terracoin-announce@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/terracoin-announce
TRC diff when up from 58K to 175k in... 20mins? in 3 jumps.
coinotron back online @ 700+Gh/s
Quote from: crazy_rabbit
TRC has shown that there is an additional computational vector for attack: A difficulty based attack. You can make the chain diff level so high that it slows the rate of production of blocks to the point where the network is at a standstill. Could happen for Bitcoin although you'd need a crazy powerful system to do it.
What would happen with ppc ?
1. i point my popular btc pool to ppc for a while,
2. difficulty starts skyrocketting
3. miners leave
4. repeat 1+2 when needed
how long would it takes to POS to bring difficulty down to a reasonable level back ? Isn't POS efficiency related to the number of running nodes and their coin age ?
by the way i'm not sure p2pool is the best way to mine TRC now, i remember an issue (now vanished in limbo) where dev said he was contacting p2pool dev about unusual orphan blocks, and per-block retargets
Can anyone explain this?
I stopped mining TRC 3 hours ago (P2Pool) but 23 minutes ago my client suddenly said "incoming!":
I stopped mining TRC 3 hours ago (P2Pool) but 23 minutes ago my client suddenly said "incoming!":
p2pool always worked like that, PPLNS, you gather shares while mining, then every single block solved by p2pool will include you in payouts as long as you have valid shares in p2pool share chain (that number will decrease with others mining after you stopped)
dustcoin.com/mining is on block 104396 with difficulty 12265.71592580. I think I've been on top of updating terracoind from the latest github source, despite the devs ridiculous lack of communication and short release schedules.
https://sourceforge.net/mailarchive/forum.php?thread_name=5168555B.1080905%40gmail.com&forum_name=terracoin-announce shows an email sent yesterday, but that one was indeed quite brutal (24 hours before it becomes mandatory)...
To test things I did two things now:
I sent 0.5 TRC to BTC-E on the old address that I use for a while now.
Then I generated a new address in BTC-E and sent another 0.5 TRC.
All for the sake of science
Now wait if they show up @ BTC-E... If they don't it's borked?
I sent 0.5 TRC to BTC-E on the old address that I use for a while now.
Then I generated a new address in BTC-E and sent another 0.5 TRC.
All for the sake of science
Now wait if they show up @ BTC-E... If they don't it's borked?
unless btc-e simply stops polling the old funding address, once a new one was generated?
All IPs listed above were submitting or relaying invalid blocks, which is very bad thing so banscore went from 0 -> 100 immidiately. Listed IPs are of
those who use older wallet versions, so not neccessarily an attacker but I've listed them anyway. From my perspective, there is not so much difference
between ignoring mandatory updates and intentionaly attacking the network.
those who use older wallet versions, so not neccessarily an attacker but I've listed them anyway. From my perspective, there is not so much difference
between ignoring mandatory updates and intentionaly attacking the network.
I am in this list. I compiled the client from git master's head less than 24h ago. What nonsense is this? The chain is forked by the devs at a whim?
Same for me. As soon as I saw the new client and before I started mining at P2Pool, I updated my client to terracoin-0.1.3-33-win32.
I only setup my P2Pool 7-8 hours ago because multipool.in was giving me trouble again and I wanted to mine TRC.
I'm looking around but can't find any newer, so I don't think the problem is at my side.
But I still get banned.
it may work the other way too : you're getting banned by remote nodes still using an older client ?