This week we gained a decent amount of miners from the XMR community. Welcome 🙂 Thank you for helping us grow as a network.
This is a place where anybody in our community can submit a post about the TRTL project they’re working on. It’s a great way to attract helpers for your project and show people what to keep an eye out for. We encourage you to show works in progress as well as finished products, as we’re happy to see them all and it shows that we’re an active community.
Turtle Wear 2.0
So Turtle wear 1.0 has been around for a couple of years now. One of the biggest annoyances I had when making it was the reliance on a companion app in Android which blocked off iOS and Standalone watch owners from using it. Turtle wear 2.0 is now a standalone application meaning it can be used regardless of your phone and work just fine! It’s also up to date with the latest play store requirements so it’s no longer in danger of being kicked off the app store at the end of the year.
I’ve been working on adding fee per byte to the TurtleCoin codebase. This is where the minimum fee for a transaction is defined by how large in bytes the transaction uses. It makes sense to charge by this metric as the nodes both have to store the transaction and they have to process the transaction, and large transactions are slower to process.
So far I’ve added the code to WalletBackend which drives zedwallet and wallet-api, just need to add it to the daemon and turtle-service. I’ll also need to add it turtlecoin-wallet-backend which drives TonChan and Proton, but that’ll be relatively easy as the codebase is quite similar to WalletBackend.
Hey everybody, there’s a new version of Proton Wallet out now as I’m sure your wallets have already notified you. Check those digits, we’ve made it to v1.1.1! Sick trips!
This is basically a bug fix release. Z and IBMCD were kind enough to find and squash some bugs in the backend that I use for the wallet, as well as some user-reported bugs related to wallet creation and some other things. (Check the changelog if you want the intimate details.)
IBMCD has implemented strict version-checking on his blockchain cache as well, so you’ll find if you do NOT update to the newest walet, your wallet may no longer sync at all. So please update!
Thanks again everybody. As far as what’s next for Proton, I’m planning on beginning work on implementing subwallets (ie, multiple addresses in one wallet file) just as soon as we get deterministic subwallets merged into the backend.
This is the place to mention someone in the community who has done something nice or deserves recognition.
greywolf i can’t thank zpalmtree enough for being the only one with the patience and tolerance to answer the numerous questions from a normie one who is one step away from being tagged with the spoonfed role. i learn slowy, and much of this shit is way over my ability to easily grasp. he is the only one who still exemplifies the qualities of being a good turtle that i read about early last year in an article in Medium that i got linked to from a tweet that was part of a series “What is xxxx”, in which new cryptocurrencies were highlighted every week. that story brought me into the community, and zpalmtree has been very helpful to me all along the painful journey.
japanesecar As always, great group! Happy to support it and thank all of you for doing the same!
anon applause to the developers and contributors who make this happen
Zpalm Congratulations to teacup for winning the Christmas discord logo bounty. If you hover over the discord icon now, it should snow animated snowflakes.
It’s been a while since we’ve interviewed a member of the team and as we just added a new Core Contributor last week it just felt right to pick back up on the article series. Enjoy!
RS: ExtraHash, thanks for taking this interview! You’ve been in the TRTL community for a few years now, and over this time we’ve watched you grow from a normal user to the developer of our default GUI wallet, and now a core dev, in fact! At the end of this interview, I hope the readers get to know you and your projects as well as the rest of us have, and maybe if we’re lucky it will bring people a little bit closer to one of the people that makes the tools they use daily.
So to take it from the top, how did you find TRTL? Do you remember what brought you here initially?
EH:I found TRTL very early on, within the first month of launch, through a thread someone had posted (where else) on /biz/. It was my first foray into getting involved into a fledgling coin, and let’s just say I didn’t really know what I was getting into. In fact, at the time, I had very little background knowledge of blockchain in general. It was a great experience, and before long I was up to speed on alot of basic blockhain concepts due to the helpful and educational nature of the community.
RS: How long would you say you were a regular user before you got the idea you wanted to be a dev? What was it that made that change?
EH:I didn’t decide to take steps toward becoming a developer until I had already been in the community as a regular user for a bit over a year, sometime in February 2019. I’d say there were two major events that spurred my transformation:
The first event was a video that you actually posted in #general, a movie on open source software and Linux called Revolution OS. It really struck a chord with me. Watching that video made me realize what open source actually was: it’s more than just opening your source code for others to inspect, it’s a revolution and community movement based around allowing others to use and modify software and change it as they see fit. This understanding was eye opening for me, and gave me a bit of a different perspective on TurtleCoin and our community.
The second event was the event that actually spurred me to start writing code. Madk had a bot in the market server that was able to give statistics on the network and market: price, hashrate, and so on. He made some changes to the bot that I did not like. So, instead of asking madk to revert the changes, I set out to write my own bot to take its place. That bot became my first ever coding project, and is still running in the market server to this day.
RS: That’s cool, and I’m not sure many people knew that about you. What brought you from doing a chat bot to wanting to design the now default GUI wallet for TRTL?
RS: What does walletbackend-js do for you, or I guess, for Proton?
RS: Is there a vision behind what you’re trying to create? Has becoming the default GUI wallet changed how you feel about the trajectory of Proton?
EH: Well, to be honest, the intention was always to become the default GUI wallet. Eventually I’d like to add multi-coin support for some of the other bigger coins, I think it’d be neat to have a fully open source client-side multi-coin wallet. However, for now, I’m just focused on improving Proton and making it the best possible experience for users on the TurtleCoin network. If anyone would like to see specific features implemented, please feel free to make an issue on the GitHub page with the feature request.
RS: What are some features you’re working on currently that we will be seeing soon that maybe some aspiring developers reading this can help with? Do you have any Good First Issues?
EH: I’m currently working on a search function to search any information locally in the wallet. It’ll match contacts in the new address-book that will be releasing next version, as well as hashes stored within the wallet such as tx hashes and payment IDs.
The issue list is looking rather slim at the moment, but I am having one issue with a module called react-select I’m using on the send page for the address input: you can’t access the context menu to paste via mouse click because the real input width seems to automatically resize based on input size. This would probably be a good one to try and tackle.
RS: For anybody who’s reading this who may want to help, can you touch briefly on the different parts of the tech stack that Proton makes use of? It uses nodejs, what else?
EH: Sure. At its root, yes, it’s a nodejs application. It’s also making use of electron, a framework for developing with web-based technologies on the desktop, and react, a front-end framework for web applications. It’s also making use of redux, react router, and webpack on the web-application side. We’re using bulma for the CSS. Of course as we’ve already mentioned, the TurtleCoin network interaction is powered by wallet-backend-js. I’m also using several tools to make up the development environment like eslint and prettier for code linting and formatting, and react-hot-loader for hot refresh in dev mode.
RS: With a list of technologies like that you’re bound to snag someone’s attention! Extra, thanks for this interview. Is there something we didn’t cover that you want to share with everyone?
EH: Thanks for having me! I’d just like to say thanks again to the TurtleCoin community and especially the developers that have helped me along my path to becoming a dev; particularly zpalm, ibmcd, mary, rock, fexra, and anybody else that’s helped me out along the way. Because of you all I’ve discovered something new that I’m really passionate about and I see myself doing for the rest of my life. I also look forward to getting more actively involved in core development and leaving my own mark on the core TurtleCoin codebase.
This is a place where anybody in our community can submit a post about the TRTL project they’re working on. It’s a great way to attract helpers for your project and show people what to keep an eye out for. We encourage you to show works in progress as well as finished products, as we’re happy to see them all and it shows that we’re an active community. To submit your post, click this link
I made some great progress on the Nvidia backend for violetminer this week. It’s now working, and hashing at a pretty decent speed. There are still a few more things I need to fix before making a release, however. Firstly, it instantly crashes on Windows 10, due to Windows 10 seemingly reserving about 20% of GPU’s vram. When I limit the memory usage, the performance suffers, so am not sure how best to solve this issue yet.
Secondly, I think I need to alter my code to use streams instead. With the current method, the CPU spins in a loop waiting for the kernel to finish. I believe this is the cause of hashrate being significantly reduced when CPU mining is enabled – the CPU is too busy mining itself to wait for the GPU kernel to finish.
I’ve been working on getting all the automated CI builds working with CUDA, so people don’t have to compile themselves. So far, Linux with both GCC and Clang are working, and so is Mac OSX – but Windows is being a bit of a pain to find the installed cuda toolset. I think I’m getting pretty close to fixing it, however.
Oh – I also need to check the miner works correctly on multiple GPUs. I think I’ve done the programming right, but don’t have multiple GPUs myself, so can’t really test.
I probably also need to add an intensity option for people who don’t want to run their GPUs at max speed.
Auto optimization is now functioning as expected, so your wallet is always ready to send the max amount possible
Using pre-generated key images to speed up transaction creation
Improving error messages returned when the daemon fails to process our transaction
Lots of logging improvements to help out developers debugging
Together with ExtraHash and iburnmycd we’ve also been doing a lot of investigation into some rare issues with wallet syncing, and wallet transacting. A ton of bugs have been found and fixed, so hopefully we’ll see a lot less of those weird issues when utilising the js backend or the blockchain cache.
It looks like the library is getting a fair bit of usage in different projects – I’m seeing the library getting downloaded over 130 times a week, and is now being included by at least 24 different projects on GitHub!
I have a few more interesting features I hope to get added in the next couple of weeks, so stay tuned ;o
This week I have had time to work on the client side web wallet. The wallet creation, storage and retrieval process is functional as seen in the above video. Next is to create a dashboard that will feature incoming and outcoming transactions; transfer capability; browser integrated notifications; remote syncing support; and export/import wallets. All wallets are stored in localStorage in encrypted JSON format.
BLOC GUI MINER
BLOC GUI Miner is a beautiful, easy to use, Graphical User interface for mining multiple cryptocurrencies based on cryptonote. The BLOC GUI Miner is easy to use and makes you getting started with mining cryptocurrency on Windows, MacOS and Linux in no time.
It is aimed at getting people that have never tried mining before with a focus on accessibility, security and simplicity.
BLOC GUI Miner support two very popular miner backends: xmr-stak and xmrig
BLOC GUI Miner comes with XMR-STAK 2.10.7 and XMRIG 3.1.1 already built-in, including configuration files for CPU and GPU mining in most of the cases.
What’s new in v1.1.1 ?
A lot of updates in this release. BLOC GUI Miner now support following crypto-currencies:
TurtleCoin (TRTL) (New Chukwa Algorithm supported)
Adding support to mine cryptocurrency: Monero (XMR), Haven (XHV), RYO (RYO)
XMR-STAK.log is now created while using XMR-STAK miner with BLOC GUI Miner
Updated miner setting to support the latest version of XMR-STAK v2.10.7
Updated miner setting to support the latest version of XMRIG v3.1.1
TurtleCoin now changed to Chukwa CPU mining algorithm
Fixed a bug that changed the XMR-STAK CPU config when changing thread count
Fixed draggable windows on macOS
Added new cryptunit widget built-in
Fixed Coinggecko stats for each supported currency
Added new box with image and link on the left custom for each coin
1st pool now automatically selected on 1st run
Added simple menu selector in the pool settings. Mining from CPU or GPU. (Corresponding port will be automatically selected on the mining pool.)
Fixed infinite GUI errors coming from electron
Added price usd for informations section
Updated XMR-STAK exact config file to latest 2.10.7
Added an experimental functionality to recover when xmr-stak stats stop to restart the miner
I put up a simple Google Form to gather stats about mining hardware/software combos. Contribute your stats for others to have a reference. The form is pinned in the #mining channel on discord for future reference as well.
Updated the guide for running NinjaRig (XMRig) on Android via Termux if you’re into that kind of thing 🙂
Thanks to Haifa Bogdan Adnan for NinjaRig it has been a bit of a hit with the move to chuckwa PoW hashing algorithm. As mentioned in the guide had to remove a part of the code to make it work on Android, hence why it pulls from my repo, which is kept up to date with upstream.
It’s always good to be recognized! These are the people who gained new roles in the community this week!
DJ – Teacup, Zerouan, rogerrobers, zpalmtree, muf, bratovenhurt
Developer – Bogdanadnan
Contributor – June, sajo8, farhod, PStarSR
Good First Issues
Good First Issues are tickets that are marked as ‘easy wins’ for new developers. If you want to be a TurtleCoin Developer, these are great tasks to start with!
Use matches property in ApiDispatcher regex #862 Some calls in the ApiDispatcher use a regex, for example, getTransactionDetails. They then extract the query parameters. We could instead extract hashStr using the matches property on the req object, by adding a capture group to the hash regex. https://github.com/turtlecoin/turtlecoin/issues/862
Remove no longer relevant asserts #811 Since pretty much everyone runs the daemon in release mode, instead of debug mode, we’ve ended up where we have a number of asserts which constantly trigger, due to altered/moved/rewritten sections of code. https://github.com/turtlecoin/turtlecoin/issues/811
Daemon+WalletBackend timestamp adjustments #704 The current /getwalletsyncdata rounds a timestamp to midnight. Depending on what time of the day you start a fresh wallet, you may have no blocks to grab (we need to roll back a bit more than we currently do with the timestamp adjustment), or too many (since it’s rounding to midnight which is quite far away). https://github.com/turtlecoin/turtlecoin/issues/704
Pay With TRTL
In Discord we have a channel called #Merchandise where people can post things you can buy with TRTL. To view items for sale, check the pinned posts in that channel. These are a few of the items from this week.
‘Halo Reach Collector Edition for Xbox 360’ by Dustin Thewind | turtleland.fun#1350 ID: #032088
‘Logitech MX Master 910-004337 5 Buttons 1 x Wheel USB Bluetooth Wireless 1600 dp’ by Dustin Thewind | turtleland.fun#1350 ID: #027270
Provided by fipsi#0789 and DroppingThePacketsHard²#4751
Rig Of The Week
Do you have a TRTL mining rig you want to show off? Tell us about it!
This is a 4 vega56 Rig – 3 Radeon Gigabyte vega 56 and 1 Asus Strig Vega 56..Currently mining as is (waiting for an actual open mining rig case to show up) on stock settings No secrets at all.. got a good room temp of 18-20 C and ninjarig is kickass with AMD GPUs HashBrownie 240 KH/s
This is a spot to spam anything TurtleCoin related that you would like to advertise, it’s free to put an ad in the roundup.
Hi fellow turtles 🙂 TurtleAds just launched! On TurtleAds you can advertise you node, pool or any other service using Turtlecoin. If you are a website owner, feel free to include your script and start earning Turtlecoin immediately. Make sure to sign up today and start earning or advertising. Regards, fipsi#0789 🙂 https://turtleads.org/
Shoutouts & Thanks
This is the place to mention someone in the community who has done something nice or deserves recognition.
greywolf thanks to those that were helpful in the past year with issues with my public node. but the latest update killed me and I can’t figure it out so I pulled the node down. thanks again to all those that did help before and I wish the rest of you good luck with public nodes still running, going forward.
@MrLahaye Thanks @Rocksteady for buying my old NES on the #merchandise channel. My second item sale using TurtleCoin. 😀 Who’s gonna be my next buyer?
greywolf a big thanks to zpalmtree for helping me get my public node back up, and also to iburnmycd for fixing my github errors in updating the nodes list.
wll1rah bogdanadnan, thanks for the great ninjarig miner and the help that you have provided in getting to work with mali GPU with OpenCL.