Our community blogs
Version 3.0.0 of the wallet has been released, finally ditching the “beta” tag for a standard release! As usual the release includes a handful of fixes which can be found in the changelog (GUI). Support for Mac OS should be fixed with this release as well. In previous beta releases there were issues with the proxy portion of the wallet, but the bug has been resolved in our testing environment. We look forward to receiving your feedback in our Discord or through one of our other social media platforms.
After the blockchain timestamp attacks last month, we implored exchanges trading Lethean to increase the required confirmations to 200. This change was made to protect our project from double spend attacks. This confirmation number was decided upon to ensure that in the event the blockchain is attacked, we would have ample time to take action.
The past 15 days have been busy for the marketing team, and we have some great achievements to show for it. Perhaps the most notable event that has occurred recently is our listing on BITKER. This new listing is an exciting milestone for Lethean. Given BITKER’s positioning in the Chinese cryptocurrency market, this listing now offers us greater exposure to Chinese users, who are among the groups of people that use and need VPNs more than most other countries in the world. It is a huge step forward, and we are very glad to be on BITKER’s platform. You can find more information about both our listing and BITKER itself from our last update, which can be found here.
Following the recent listing, some community members have had concerns over certain aspects of BITKER’s operations, and some of the statistics used in our press release. We would like to let the community know that we have heard them, and we released a response a few days ago addressing these concerns. Our response can be found in this article.
Our listing on BITKER is only the beginning of our efforts regarding exchange listings. We are still reaching out to many different exchanges and attempting to get listed on them as best as we can. We are doing this because we want to ensure that users have a variety of different options to acquire Lethean, and thus be able to utilize the service that we provide. We are working harder than ever to meet and exceed community expectations. We are aggressively pursuing exchange listings, capital investments, and formal investments. Formal investments and capital investments will make getting listed on exchanges much easier in the future.
Advertising campaigns update:
With the recent listing on BITKER, we have been working hard at capitalizing on the exposure we now have to the Chinese market. The above image shows some data from our Chinese ad campaign. It currently boasts a clickthrough rate (CTR) of 2.48%, which is well above the industry average for display network ads of 0.84%. We are very proud to have a marketing strategy that performs well above industry standard, and we will keep the community informed of any other major milestones as they occur. Furthermore, to complement our current advertising positions, a series of Medium articles are being developed to highlight the competitive advantages Lethean holds over its rivals and our role in eliminating online censorship.
We are in the process of updating our website to offer support for multiple languages. Currently, our site utilizes Google translation services. We recognize that the translations are not as accurate as they could be. For this reason, we are working in tandem with our community to offer a better experience for non-English communities. Our focus for now is to integrate native translations in Chinese, German, Portuguese, and Russian. We will keep the community updated on when manually-translated versions become available for use on the website.
Alex at Bit Thailand:
Alex recently visited BIT Thailand. During his time there, Alex was given the opportunity to network with exchanges and leaders of other projects. We are very happy that Alex was able to get the word out about Lethean at this event.
50K Lethean Discord contest:
Following the success of our previous series of puzzles and riddles, we began a new puzzle-based contest on our Discord nicknamed the “Puzzle Party”. A series of five puzzles were found in the #puzzle-party channel in our Discord. Each puzzle, when solved, gave the solver five words from a mnemonic recovery seed to a wallet. When these words were used to recover the wallet, the winner found 50,000 Lethean waiting for them. As of November 12th, the puzzles were all solved and the prize was claimed by one of our Discord community members. We greatly enjoyed making these puzzles for the community, and we may look at organizing similar events in the future.
We are very excited to see our Telegram channel growing as rapidly as it has in the past two weeks. We have had approximately 150 new users join our Telegram channel. If you need assistance at any time, please feel free to reach out to us on any of our social media channels below.
- Read more...
- 0 comments
This week was one of the best yet! Between playing the games you guys made with your TurtleCities pages, and ones you wanted to watch on TwitchTurtle, I’m spent! Awesome community participation this week, and we’re really looking forward to next week!
Trtl Driver — As turtles we all have a need for speed, scratch that itch by playing the “Turtlefied” version of Yu Suzuki’s arcade classic “OUTRUN”. Discover this and many more games @ “games.turtacus.com” — a showcase for all the diverse talents of the TRTL community. If you want your game/ project featured or are interested in learning more about game development, please message me @ Trt.Simulator@gmail.com or drop into the TRTL Discord! — Oiboo
TurtleCities — Wow, it has been a big week for all of you that put up homepages on TurtleCities! For those of you that don’t know, we made a just for fun project last week that lets people sign up for a single floppy disk worth of web hosting for an old school home page and to show the internet just how cool you can be with only 1.44mb to express yourself. I’m still deciding on “upgrades” to offer, but currently thinking about doing a “Dual density floppy upgrade” for 2,000 TRTL, and I’d like to see what adding some shell accounts to certain users would be like. The obvious next step is to release the BBS system I’ve been tinkering with…. But that’s another story :D -RockSteady
TurtleEDU — I’ve completed all of the course material for the first course on TurtleEDU, which I’m going to call “TurtleCoin 101”. It’s a class that will take someone who is new to cryptocurrencies and turn them into a certified TurtleCoin user by the time they finish. It doesnt take long, and the class is divided up into easy sections. I’d like to add some finishing touches, but I get the feeling I may be overdoin it, so video/audio content might wait until after the beta launch for people with the “student” role. Remember, if you’re interested in being a trial user of TurtleEDU, be sure to type *student in the discord to automatically enroll you in Turtle School :D
The next classes I'd like to work on are "Contributor 101" which will guide the user through how to use Github for version control to create and modify guides and wikis, and then "Developer 101" which will be a guided tutorial to using the TurtleCoin API using the docs on https://api-docs.turtlecoin.lol
Fexra is still working on the visual theme for TurtleEDU, and we'd like to get it skinned up before you guys get to try it out on December 9th, our one year and 1 million blocks anniversary! - RockSteady
Core Team Update — A new core developer has been officially added to the team. He has significant amounts of contributions to the core suite and is the project leader behind the Golang port of the TurtleCoin Core Suite — We are very pleased to introduce Rashed to you guys :) You are probably already well acquainted with seeing his name in the roundups and hearing about him in podcasts, and we’re very excited to bring him aboard. Great job, sir! — RockSteady
lite-blocks — This is the TRTL version of XMR’s Fluffy Blocks which is being implemented to increase the propagation of blocks in the network in a much efficient and faster way. Work is progressing slowly day by day as I am in middle of my semester exams.
So what are lite-blocks? We all know that new transactions propagate throughout the network and are stored in the transaction pool of every daemon.. whenever a miner finds a block the daemon removes those transactions from the pool and adds them to the block and then propagate that block throughout the network.. you see transactions are a heavy thing.. they make up most of the size of the block.. it is just an overhead to send the transactions again which the other daemon already has.. also since it increases the payload size it would take time to propagate it throughout the network.. To solve this problem instead of sending the block with all those transactions we just send their hashes which are much less in size.. the receiver checks for those transactions in its transaction pool.. if it has all of them it creates the block by itself and adds it to its database.. but if it couldn’t find any of those transactions.. it requests the sender to those missing transactions only.. hence the lite-blocks essentially contain the block header and the transaction hashes which are present in it or it contains the block header along with the transaction hashes and the requested transactions.. this technique will help reduce the payload for the propagation of block throughout the network and hence result in much healthy network and I guess less orphans too — rashedmyt
Windows on Travis — Got bored by studying for my exams and thought lets take a look whether travis has given support for c++ projects on windows or not. To my surprise, they have supported it very soon and I thought lets get the work started. After working for a couple of hours to figure out how to get started and get things done, also not to forget the long waiting times for the build to just see the red error messages. I have finally managed to get the build working perfectly and deploying. Thanks to iburnmycd and zpalmtree for helping me with disabling the builds to just test the windows build. — rashedmyt
trtl.rocks — Here is a quick breakdown of what I’ve done on http://trtl.rocks over the last two weeks — andrew | trtl.rocks
• Restructured the database
• Added fuzzy search and pagination to the nodes and pools page
• Added node fees to the node table
• All The Pools — expanded the pool service to grab data from forknote and node.js pools, as well as cryptonote.social
• Added pool fee types, when available
• Updated the pool hashrate graph to display unknown hashrates
• Fixed mobile nav
TurtlePay™ — Quite a bit of progress has been made this week in the Blockchain Data Collection Agent (BDCA) with the sole purpose of collecting and caching the blockchain in a database friendly way. Building a strong backend distribution system for TurtlePay™ is paramount as the scale and flexibility is at stake. Returning data as quickly as possible gives us the ability to scale to massive unprecedented levels seldom seen in Blockchain applications. Initial testing has shown the ability to provide data to the wallets at a rate of about 100,000 blocks per minute. The payloads provided to wallets are substantially reduced in size to include just the needed information for scanning for funds sent to our wallet(s). As a byproduct of the streamlined payloads it is possible to create a fast, efficient, and versatile block explorer built on this database backend. Look forward to more information to come in the coming days and weeks and keep up with the latest information in #dev_turtlepay — IBurnMyCd
Swanson Clicker — Swanson Clicker has come a long way in a short amount of time! Thank you to all the ~76 unique users who have clicked Swanson whether that would be 1 time or 1,000 times! Hopefully your Pineapple Farms and Snail Racers are doing great. In the future, I will be attempting to gracefully implement items and more statistics so bear with me if you lose your progress. If you have not tried Swanson Clicker yet, then you’re missing out! Special thanks to Oiboo in discord for this awesome title-card for Swanson Clicker. — Xaz
WalletBackend / WalletGreen rewrite — Finished rewriting zedwallet this week with the new wallet-backend I’ve been working on everything seems to work well. Apparently it has some issues on Windows. Shouldn’t be too much effort to fix, though. I started writing some documentation on the wallet file encryption format, and the wallet JSON format. You can get that here — https://github.com/turtlecoin/wallet-file-interaction if you’re interested in interacting with wallet files manually, perhaps to build your own wallet backend implementation. I’ve got some examples of how to open a wallet file up there, currently in C# and C++. If you’ve got a favorite language and you think you’re likely to want to be able to open wallets without the help of an RPC interface, let me know, and I can probably code up an example for that language too. Next I need to get turtle-service rewritten, so you can make API calls to it from all your favorite languages. Oh — I finished writing that article I was talking about on how transactions work. Just giving it a bit of a review then it should be ready to publish. Thanks to IBMCD for reviewing my code :)) — Zpalm
Article — I wrote that article on transactions I was talking about in past roundups — you can check it out here. It goes into depth on how wallet syncing works, and how a transaction is made — it’s a bit complicated, but hopefully a few people can learn something — Zpalm
2,500,000 TRTL — Submit a PR, and have it accepted, to add MULTI-SIG wallets to TurtleCoin and receive the following bounty. — TurtleCoin Core Development Team
+500k from IBMCD
+500k from Zpalm
+500k from RockSteady
+500k from fexra
+500k from Slash-atello
1,500,000 TRTL — Submit a PR, and have it accepted, to add RINGCT to TurtleCoin and receive the following bounty. — TurtleCoin Core Development
+ 500k from IBMCD
+ 500k from Zpalm
+ 500k from fexra
75,000 TRTL — I need a quick site done up with a simple (very simple) shopping cart interface that does the following — GNU/Ashmedai
1) guest selects “purchase access”
2) guest is given an address and payment ID to send the amount of TRTL to
3) once TRTL is received, guest is granted the ability to download a file up to 5 times.
4) upon limit reached, access to file is denied.
Bonus bounty: +25K TRTL if TRTL.Services is used. Project will be used to host a TRTL blockchain bootstrap.
0 fee nodes; greywolf London turtlenode.me:11898; and greywolf Germany turtlenode.co:11898
Looking for a rock solid, highly available public node to use with your wallet? Look no further than the ORIGINAL TurtleNode.io. No, our fees are not the cheapest in town but we’re the oldest, longest running, public TurtleCoin nodes in existence today. Why fight with the rest when you can enjoy the best! — https://turtlenode.io/
Interested in mining on a set of pools, with 3 locations worldwide? Look no further than http://turtlepool.space! Turtlepool is the oldest turtle mining pool, only a week younger than TRTL itself! Locations are: Hong Kong (with direct china route), London, and Dallas. Support offered in English and Russian — http://turtlepool.space
Mine2Gether invites you to our weekly Blockchain Bingo
The next Blockchain Bingo is Saturday Nov 17th @ 18:00 GMT in our discord #bingo channel. Community super fun, open to everyone, and completely free to play! It is a variation and similar to traditional bingo, and uses the turtle blockchain to draw the numbers. Everyone is welcome! 25K TRTL prizes, 100K jackpot, slots mini game, and more!
Each winner will also direct the amount matching their prize towards the turtle development bounty of their choice. (for example, if you win 25K we will direct an additional 25k to the bounty of your choice on your behalf.)
Hope to see you there!
Bingo Site: https://bingo.mine2gether.com/
Bingo Discord: https://discord.gg/AT3AAxV (#bingo channel)
Converted date and time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Mine2Gether+Blockchain+Bingo&iso=20181117T18
Shoutouts & Thanks
Oiboo — Big thanks to Rynem for the Webspace! :D ❤
GNU/Ashmedai — Shout out to ison for his wonderful work on the WalletBackend re-write. It’s times like this that I get excited for what the future holds for the project!
IBurnMyCD — Yo to the AmityCoin crew for their first week running the first consistently running Soft Shell mainnet.
rashedmyt — Thanks to RockSteady and the entire community for recognizing me as one of the core developers..
mufalo — Special thanks to zeto sama for being so nice when i have dumb logic-code troubles
Xaz — Special thanks to Oiboo for linking to Swanson Clicker on his arcade site! 🐢🐢🐢
arms — Shoutout to all the devs and community members for constantly building great things and being awesome!
anon — thanks for keeping the chat an education place for users and trader-free.
Name of your TRTL fork: CyprusCoin
Github link for your code: https://github.com/CyprusCoinClub/CyprusCoin
What is special or new about your network?:
CyprusCoin completely focused on Offshore business and investment market. We have built CyprusCoin as a fast emission Cryptonote coin that aims to provide users a secure environment to handle their funds. On the technology side we are trying to have an advanced but at same time easy to use interface that will help everyday users to manage their funds safe and securely.
Originally published at TurtleCoin.
- Read more...
- 0 comments
We are super excited to announce the next release for Loki, which will contain Bulletproofs, along with a few larger quality of life changes for Service Node staking.
- Add Bulletproofs;
- Lower transaction fees in accordance with Bulletproofs;
- Add staking from the GUI wallet;
- Governance wallet payout changed from once per block to once per 5,040 blocks, this reduces blockchain bloat;
- IPV6 Support for Loki Daemon and Loki wallet CLI;
- Zawy difficulty adjustment algorithm patch;
- Service Node grace period added, Service Nodes that consecutively register within a time frame at the end of their staking period will not be deregistered;
- Fix for the common “No known outputs” bug;
- Integration testing framework;
- Increased visibility of when locked amounts are being received;
- Increased visibility for the unlock time of staking transactions;
- Add the SwarmID field to all Service Nodes which provides the framework for the logical grouping of nodes;
- Merge Monero upstream, this includes over 1,000 commits that Monero has added over the last three months;
- Merge Monero GUI Upstream which fixes a number of bugs in the GUI wallet;
- Add versioning to Service Node uptime proofs — nodes reporting old versions past the hardfork will be de-registered.
Below is the schedule for the hardfork, with all changes available for testing on testnet between the 20th and the 30th of November. We encourage everyone to jump onto testnet soon so that the team can find bugs and update binaries before the 30th of November, when the final binaries will be released.
Who needs to update?
Everyone — including users, miners and Service Node operators. Once the hardfork occurs, you will not be able to send Loki unless you update to the new wallet.
Will my Service Node be affected?
Yes, in this hardfork we will be adding an extra field to uptime proofs: each node will report its version number, and nodes exhibiting the incorrect or no version number will be deregistered as a result of quorum testing. To ensure safe operation, you must update your Service Node to version 2.0.0 (Festive Freya) before 13 December 2018.
We have made an instructional video guide on how to safely update a Service Node, here.
Will Autostaking be affected?
Yes, although we are not making any specific changes to autostake, the introduction of bulletproofs makes old wallets incompatible with the protocol upgrades. This means that if you want to autostake, you will need to shutdown any running Loki wallets (listed as loki-wallet-cli) and start a new autostaking wallet that can submit transactions with bulletproofs.
- Read more...
- 0 comments
GRAFT Development Status Update November 12, 2018Today is a very big day for GRAFT project – we’re releasing the new baby into the world!
The RTA Supernode is a linchpin of the GRAFT project, allowing the real-time transaction authorizations. To get to this point it took a lot of work engineering reliable transport protocol, supernode sample selection, all in a maintainable and modular way.
With the RTA Public alpha release, we’re opening the testing up to the wider public to further test and optimize its performance and reliability.
How to participate in RTA Public Alpha
- Follow these instructions to install the RTA supernode
- Submit this form to request the alphanet supernode PoS stake.
- Join the RTA Alpha Telegram group to get more info about the testing process and share your findings and ideas with the community and developers.
What kinds of goals is RTA public alpha pursuing?
There are several goals for the RTA Public Alpha testing stage:
- Find potential issues and bugs that cannot be found on a low scale network of closed alpha (about 50 participants/supernodes)
- Allow supernode owners to get familiar with the supernode setup and maintenance processes so they will be fully prepared for the RTA Beta launch on the mainnet
- Allow the supernode owners to estimate the earnings on the real network (the stimulus transactions will be running on public alphanet on the same or similar scale as they will be available on the mainnet after the Beta launch)
- Most importantly, work on preparing the network for the mainnet launch by allowing community to discover any security holes and potential exploits
What to expect?
- November 12 – the RTA SN instructions are available to the community to build their RTA supernodes, configure them and connect to the Alphanet (RTA Alpha testnet)
- November 14 – Transaction simulator availability – a special bot that will generate regular test transactions in the system
- November 15 – Alphanet hard fork to enable the latest release of RTA supernodes and client apps; Wallet/POS RTA-compatible clients updates available via Apple app store
- November 26 – Stimulus Tx package testing…
How long with the RTA public alpha last?We don’t know what kind of things are going to get uncovered during the course of the public alpha, so it’s hard to put a date on the Mainnet beta release. 8 weeks is a good case scenario, but at this point it’s a rough target.
How to report bugs / suggestions?Please funnel the bug reports and suggestions through our community dev liason – Jason R @jagerman..
- Read more...
- 0 comments
In this update we will discuss the following:
- Service Nodes
- Hashing algorithm and difficulty algorithm fork
- Community Questions
- Twitter giveaway
- The Swap
Service Nodes has been live on the Saronite blockchain since block 5000. Since the start of service nodes, there was a total of 46. Three of them has been de-registered from the network. We ask everyone that’s running a service node currently or plans to run one, to run them on stable servers and avoid home computers at all cost. When a service node de-register. At the time of writing there is a total of 1.9 Million XRN has been locked away. We are also proud to now be listed on Masternodes.pro. You can visit the Saronite statistics by following this link https://masternodes.pro/stats/xrn/statistics
The Saronite whitepaper has been updated to v1.1
The following sections in the whitepaper has changed
- SaroWrite (Adjustments were made and added feature list)
- Algorithm update
The whitepaper will be updated a few times a week to show new features after we have tested some functions. We will have a permanent testnet pool running. Please note that these coins are testnet coins and not XRN.
Hashing algorithm and difficulty algorithm fork
Saronite will fork to a new algorithm on block 20000 , this new algorithm will move Saronite from being Nicehash friendly and help with better decentralization. Saronite will also implement a new difficulty algorithm provided by Zawy, LWMA Version 4. These changes will help making the block time more accurate and help the network against attacks on the blockchain. We have decided to use the same custom variant of Cryptonight Haven as all miners already supports it. After the fork block you will need to mine with algorithm cryptonight_haven.
PLEASE NOTE THAT ALL SERVICE NODES NEEDS TO BE UPDATED TO THE LATEST BINARIES BEFORE THE FORK BLOCK. THERE WILL BE MORE THAN ENOUGH TIME AFTER WE HAVE ANNOUNCED THE FORK BLOCK HEIGHT.
Saronite will be running polls to see if the community would like one of the following options before we decide on our next exchange listing
- List Saronite on an exchange that’s on CoinMarketcap (This exchange will be cheaper to list and it has lower volume, this will be achieved faster)
- List Saronite on a bigger exchange that’s on CoinMarketcap (This will take longer to save up for and it has much higher volumte)
In every update we will post questions from the community and answer them.
- Q: What can the community do to help Saronite?
- A: The community can help with social promotion (Sharing Tweets, links etc)
- Q: When can we expect a new exchange for Saronite?
- A: As mentioned above, we will give the community the opportunity to vote on what would they want to do
- Q: Are you planning to host another Twitter competition because it destroyed the price?
- A: Twitter competitions in the future will be done differently and the giveaway was bigger than what it normally would be, this was just to help Saronite slight exposure while on our road to recovery
- Q: Can I run my service node on my computer
- A: Technically yes, but it’s advised not to. A stable VPS provider will be much better.
The Twitter competition winners was voted for by the public, below are the winning images
The blockchain swap did not go as smooth as we would have liked. We apologize to those that missed out on the swap. The following happened while swapping:
- Some miners was mining on the old daemon and came to swap coins thus the “premine” for the swap was not enough and some people gotten more than what they should have.
This could have been avoided by taking a snapshot of the old chain, asking for viewkeys and other ways.
That wraps up the update for this week.
Special thanks to:
- Zawy (Difficulty algorithm)
- Cryptodude (This weeks featured update image)
- Community managers (VultureX2, JackRyan and Serg)
- Read more...
- 0 comments
Recent EntriesLatest Entry
The days of ads as an unavoidable evil are over.
It’s too good but it’s actually true!
This week’s update includes platform updates, how we’ve survived several DDoS attacks, a new website and the browser extension beta.
Video platform improvements suggested by the community.
You asked for it, we listened. The volume slider now will instantly affect the sound on slide, while before the volume was adjusted on mouse release.
On Monday 12th the following updates will go live on the platform:
Watching a playlist will show at the top the current index of the video playing and the total number of videos in that playlist.
For live streamers we made streaming keys access faster with a show/hide broadcast key button.
The profile appearance will improved. No more stretched wallpaper on your profile page. We recommend minimum image size of 1780x280px, anyway you can use the editor buttons to center, zoom and fit the background.
Every social media platform is unique and your audiences differ greatly. Early next week we will add the option to link directly to your social profiles such as Twitch, Soundcloud, VK and our blockchain friends at Musicoin.
Lastly, as always we have made backend fixes and optimizations.
We survived some major DDoS attacks
Last week we’ve experienced multiple sustained DDoS (Distributed Denial of Service) attacks, causing the platform to be inaccessible. We’ve since taken many steps to expand and mitigate against future incidents.
These were not small attacks, and we are actually in some ways grateful for this opportunity to stress-test our services well before reaching mainstream adoption. So whoever they were, thank you for making us stronger!
The home of all BitTube apps and software products now online at BitTubeApp.com
The secret to happiness is freedom, and the secret to freedom is passion. This passion allows us to think outside the box and deliver these products.
— Saber Maram, Founder & CEO, BitTube
Many great ideas sounded odd in the beginning, from Airbnb’s ‘give your home to strangers’ to Uber’s ‘ride in somebody’s car’. We are no different.
BitTube AirTime is rewarding you simply because you surf the Internet, allowing you to generate revenue for publishers without ads or paywalls. With AirTime, we aim to become the biggest perpetual airdrop machine on the Internet, creating a mass-adopted payment ecosystem. Featuring easy to use tools for transactions, donations and monetizing publishers’ content.
Check out our freshly minted website at BitTubeApp.com. To learn more about how AirTime works, visit our Knowledge Base (work in progress).
BitTube AirTime browser extension in beta
Your time and attention are a limited resource. They have inherent economic value regardless of ads. Ads insert contradictory design elements to websites. Where traditionally the revenue relies on distracting you away from the publishers themselves, instead, AirTime allows you to spend your undivided attention — and monetizes both sides. It is a mutually beneficial, ad-free, win-win situation.
That’s why we developed the browser extension. Integrated at the root of the browsing experience, like books, the browser is a window to the world (and it shouldn’t be polluted by ads).
Apply for the AirTime extension beta here.
One of the most exciting features is that it works silently on the background. There are multiple tasks performed by the extension from removing ads to inserting donate buttons on the major social platforms. The best one is that, while using the extensions, it automatically generates a wallet address on first visit for any website or social profile. In that way we respect all publishers, personalities and even retailers. Claiming the funds generated by the visitors is an integrated functionality in the extension. We are also working on a module that publishers could integrate on their domain, such that guest visitors (most of whom of course won’t have the extension installed) are also allowed to generate some AirTime. More information on this will follow in the next few weeks.
That’s all for now. Give us your feedback and join the discussion. Have a great weekend!
Your BitTube team
Join our Newsletter!
Join our Newsletter!
You have Successfully Subscribed!
- Read more...
- 0 comments
Dear X-CASH Community,
Today, November 6th at around 6PM (GMT+1), we will update the network to the latest X-CASH release 1.4 with the hardfork (V10 then V11). There will be a few major changes and exciting additions to X-CASH, such as :
FlexPrivacy©: Chose between public or private transaction with the same account
FlexPrivacy© is the most anticipated feature that we have planned for X-CASH since the birth of the project :
FlexPrivacy© adds the possibility to send a public transaction or a private transaction from the same wallet on a per transaction basis.
It will be as easy as clicking a toggle switch in the GUI, and typing « public » in front of the transfer command in the CLI.
Private transactions will work the same as before, being fully anonymous from the use of stealth addresses and RingCT. Public transactions will show :
- Senders XCA address
- Receiver XCA address
- Amount sent
- The change amount sent back to the senders address
Note: These types of transaction will never compromise either the senders r receivers wallets full balance or the real mixin of where the X-CASH came from. It is very important to keep these two details always unknown in every transaction.
This system simulates the current fiat system :
- make a transaction using a check, credit card, bank transfer etc… and leave a transaction trail (public transaction)
- pay with cash from person to person, without any outside party witnessing the transaction (private transaction)
Either way, similar to the fiat system, there is no need to have multiple accounts to pay with cash or check. Your account balance, as well as the receiver’s account balance, is never made public.
Public transactions can be enabled on any X-CASH mining pool as well, and even on a per user bases (meaning you can decide if you want them enabled or not), so make sure to check with your mining pool to see if they support them.
You can start using public transactions right after the hard fork, there’s no need to create a new account either, they are compatible with all X-CASH accounts, created at any point in time.
Revamped block explorer
With this update, we will release the new X-CASH block explorer, from which you will be able to check transactions and blocks with better visibility and clarity.The revamped block explorer will provide better reading of the blocks, and information from public and private transactions.
New additions comprise
- a separate transaction pool for better readability on the front page;
- an API tab;
- statistics on the X-CASH network;
Fixed ring size
We this update, we decided to fix the ring size to 21. Fixing the ringsize enables better privacy, as to avoid multiple and unusual ringsizes that could be used to link transaction.
We found that 21 enabled a good compromise between quickness of execution, privacy, and low impact on size.
The latest addition of Monero 13.0. Bulletproof transaction enables much smaller transaction, hence decreased fees and more transaction per blocks. From now on, the blockchain size incrementation will decrease.
We are switching mining algorithm from CNv7 (=CNv1) to new ASIC resistant CNv8 (=CNv2). It is recommended to check if your mining software is compatible with the new cryptonight algorithm.
How to update
Please read the update instructions in the GitHub release: https://github.com/X-CASH-official/X-CASH/releases/tag/1.4.0
X-CASH Major Update 1.4.0: FlexPrivacy©, CNv2, bulletproof and fixed ring size was originally published in X-CASH on Medium, where people are continuing the conversation by highlighting and responding to this story.
- Read more...
- 0 comments
This long overdue update launches SECOR & Uncle Mining on the testnet, touches on the Masari Collaboration Corner, shows off our new client-side explorer, and offers some exchange best practices among others.
November 1st, 2018 marks the successful launch of Masari’s v8 testnet. This is exciting as it features the new, original design and implementation of SECOR: Simple Extended Consensus Resolution. SECOR delivers Uncle Mining, which will increase network security, deliver faster blocks, and reward miners for their hard work that would have otherwise been orphaned.
This new blockchain feature is cutting edge, and a first in the CryptoNote space. With this groundbreaking development issues will certainly arise. To encourage code reviewers and facilitate the successful launch of Uncle Mining, bounties ranging from 100 — 10,000 MSR (depending on severity) will be given out for each new vulnerability discovered in the SECOR design and implementation. As always, the code is open source and available on Masari’s GitHub.
One of the most common complaints the core team hears about the project is that people want to help or contribute, but don’t code. Of course people can do RTs, likes, upvotes in social environments, but that doesn’t welcome nor facilitate contribution. The crypto space has seen launches of a variety of community participation programs, but they don’t necessarily resemble autonomous organizations, nor do they empower the participants to self-govern or evolve.
A framework is being drafted that will allow Masarians to contribute to areas in which they have interest or expertise — including outreach, development, education, intelligence, marketing, and social media among others. The Collaboration Corner will launch one of the most effective, inclusionary programs the crypto space has seen; and it will further decentralize the stewardship of the Masari project. Keep an eye out for the charter this month.
Masari’s old block explorer was the consummate plain Jane site. Black and white with not a lot of jazz. That is changed now with the launch of https://explorer.masariwallet.com/. The site is currently in testing and will be ported over to msrchain.net once it’s out of beta.
The new explorer is fitted for both SECOR and Blocktree - as both require overhauls of the user interface to facilitate their additions. The new explorer is also entirely client-side (verifications), which is becoming a hallmark of Masari development.
Masari PayOur beloved Masari Pay Discord bot has been under the weather for quite a while.
For the lotto participants and tippers alike, it’s been a frustrating month of October without having Masari Pay up and running. The bot has been having an issue with running too many wallets which causes it to overload. A new bot design will be spun up by Masari developer Gnock. In the mean time if you had funds on Masari Pay — they are safu. The current Masari Pay bot will be moved to a server with better capacity to transact in the near future.
Masari’s client side web wallet received some nice improvements in the month of October. You can view the history here. The web wallet is also undergoing SECOR testing to coincide with its launch.
Mobile holders can look forward to the Android wallet being added to the Play store in November, with a potential iOS version available by the end of the year. Bug reporting is still encouraged and welcomed in the phone app feedback channel in Discord.
Masari core team members will be taking part in recording two separate podcasts in November. Neither of the hosts asked for compensation, which is appreciated and encouraged. The podcast with Talking Cryptocurrency was born out of this thread in particular. The recording dates and medium are below. Please show your support to these ethical projects.
Recently an exchange that Masari was listed on abruptly closed their doors. Fortunately the losses to Masarians weren’t severe, but it provides an opportunity to talk about best practices in regards to trading MSR.
The general consensus is to keep your coins off an exchange unless you’re actively trading. For example if you send BTC to Cryptopia to buy MSR, after your purchase move the Masari to your wallet off an exchange. There have been too many exit scams and hacks on exchanges in crypto’s history to do otherwise. Regardless of the exchange’s name, history, or volume.
Additionally, as noted in the Maple Change incident, even when an exchange is incorporated and operating within the bounds of law, there will be little support from law enforcement regarding reimbursements in the event of a “hack.” All of the above can effectively be reduced to:
If you don’t have the private keys, they’re not your coins.
If you have registered on an exchange that has been hacked or exit scammed, you should also consider whether or not your email address is compromised as well. It’s a good idea to phase out the email used on a “hacked” exchange.
Discord: 2,192 members (+143 from update 6)
Twitter: 1,437 followers (+174)
Reddit: 1,138 subs (+60)
Telegram: 781 members
- Read more...
- 0 comments
Important announcement for the future of Offshore Storage!
Offshore Storage will be available based in other Currencies:
We have teased and previewed this in tweets of our vision for the future mobile app redesign:
Sneak peak #2 into the future of @HavenProtocol: What feature do you want added to the 2019 roadmap?
The concept for multi-currencies has been in place from very early on in development. Although storage of funds is a major component to Offshore Storage, the use case as a day to day payment platform is very clear. Using Offshore Storage, any user can effectively create cryptographically untraceable fiat to store and transfer worldwide.
In order for Haven Protocol to rival all traditional stable options for a storage or payment platform i.e. onshore and offshore Banks, PayPal, Visa etc on a worldwide scale, support for multiple currencies is imperative.
At this time we are planning to initially release Offshore Storage with Haven Dollars exclusively. The Multi-currencies implementation will be a future hard fork.
The reason for the change is to provide clarity and consistency for all future offshore currencies. Any existing currency ticker can be used simply with adding an ‘X’.
When considering how to identify offshore USD from CAD, AUD, NZD we would have inconsistent formats with our previous ticker format. (XHVD vs XHVCAD) All issues are solved with the addition of a leading ‘X’.
Although from a technical perspective this change isn’t an issue, maintaining consistency from a marketing and discussion perspective is important to avoid confusion.
All other documentation referencing XHVD will be updated to reflect the new XUSD format.
What Currencies are we going to support?
So far we have previewed the following:
More currencies will be announced in the future! If adding a new currency helps bring more users to the Haven Protocol platform, we will work to do so.
This is very exciting from a cryptocurrency adoption perspective for merchants. They will be able to accept Offshore Storage funds and store funds in their respective countries currency. Price stability and privacy are the only hurdles to crypto adoption — and Haven solves both.
- Read more...
- 0 comments