https://coinpaprika.com/coin/tlo-talleo/
Category Archives: News
Official Hive community
Steem blockchain was forked to Hive due to disagreement on recent actions conducted by Tron owner Justin Sun. As all the content on Steemit was mirrored up to the hard fork height, also old Talleo community on Steemit was mirrored to Hive. The new community can be browsed at https://hive.blog/created/hive-147043. We will still update the […]
Talleo has been added for voting on nanu.exchange
To see status of voting, visit https://nanu.exchange/site/voting. You can vote by sending NNC to wallet address NfxZZdmKEHdSjtwe88kH9caybZjYwiXTkn. Our goal is 10000 NNC.
Talleo Project will now accept tips from users of Brave browser
Brave is browser based on Chromium project with integrated privacy features and advertisement blocker. It will show unobtrusive advertisements if user opts-in. Users that don’t opt-in can send tips to site owners. To download Brave, visit https://brave.com/.
Wallet blacklist on official mining pool
Yesterday was the first time we ever used the feature to blacklist any specific wallet addresses… I personally don’t like using the feature unnecessarily even though I was the one who initially added the feature… Everyone should have the right to mine Talleo as long as mining doesn’t cause issues to other community members… As […]
C-PatEx added TLO-ETH and TLO-LTC pairs
TLO-ETH TLO-LTC
Official Talleo subreddit launched
Official Talleo subreddit on Reddit is now available at https://www.reddit.com/r/Talleo/.
Talleo listed on Argentine exchange C-PatEx
This week Talleo was listed on Argentina based Crypto Patagonia Exchange (C-PatEx) with BTC pair.
Talleo added to CoinGecko and coinlib
CoinGecko coinlib
SRBMiner-Multi adds support for Talleo
SRBMiner-Multi added initial support for Talleo’s algorithm in version 0.3.0, but it was a dud release that did stop mining with error 0x4002. Version 0.3.1 fixed the error, but still has low performance when mining with CPU due to incorrect detection of usable threads. Thread count should be L3 cache size divided by 256 kB.