Jump to content

Snider

Administrators
  • Content Count

    473
  • Joined

  • Last visited

  • Days Won

    20

Snider last won the day on October 24

Snider had the most liked content!

Community Reputation

68 Excellent

1 Follower

About Snider

  • Rank
    Mega Hashsaurus

Recent Profile Visitors

844 profile views
  1. Snider

    BITKER and Marketing

    Dev corner 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. Marketing BITKER listing: 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. Exchange Efforts: 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. Website translation: 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. Socials: 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. Facebook Twitter Discord Telegram (community) Telegram (announcements) Reddit Bitcointalk YouTube LinkedIn GitHub View the full article
  2. Snider

    This Week in TurtleCoin (Nov 12, 2018)

    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! https://blog.turtlecoin.lol/wp-content/uploads/2018/11/video_power.mp4 Developer Community 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 Trtl Arcade | Welcome 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 rashedmyt/turtlecoin 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 rashedmyt/turtlecoin 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 TurtleCoin Explorer 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 TurtlePay/blockchain-data-collection-agent 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 Swanson Clicker 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 How a transaction is born, and how wallet syncing works Community Bounties 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. Community Advertisements 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. Fork Watch! 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. View the full article
  3. Snider

    Festive Freya Announcement

    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. Features include: 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. View the full article
  4. Snider

    RTA Public Alpha Release

    GRAFT Development Status Update November 12, 2018 Today 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 The RTA alpha is time to find vulnerabilities in the design, from both scaling and exploits point of view. We expect the RTA alpha testers to contribute to pushing the network’s scalability limits as well as security and usability. To that end we’re working on a bug bounty reward program that will be announced shortly. 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.. Happy GRAFTing! The post RTA Public Alpha Release appeared first on Graft Blockchain. View the full article
  5. Snider

    Weekly Dev Update #22

    Hey Y’all, Another weekly Dev Update for you to peruse. Just a note, we’re moving Dev updates to Mondays instead of Fridays, so keep your eyes peeled each Monday. Loki Messenger Integrate the Service Node storage into Lokid https://github.com/loki-project/loki/pull/311 Fix conversation list showing duplicated conversations when entering a known public key https://github.com/loki-project/loki-messenger/pull/25 Fix validation of messenger public keys in search bar https://github.com/loki-project/loki-messenger/pull/26 Merge upstream changes from Signal https://github.com/loki-project/loki-messenger/pull/27 Add code to parse message TTL https://github.com/loki-project/loki-storage-server/pull/5 LLARP / Lokinet Released Lokinet 0.3.1: “Kuz Yolo” https://github.com/loki-project/loki-network/releases/tag/v0.3.1 Minor DHT bug fix release We urge all Lokinet toy node operators to upgrade ASAP as they’ll be unable to communicate as the network upgrades. Progress continues on libllarp Started on Docker support Fix endian in tun ip checksumming Jsonrpc unit tests Make sure HasPathToService actually has a sendable state Client config gen to include a sample hidden service again A lot of C++ correctness clean up Always remove DHT node even if not valid Update android version Enable warnings as errors Start to add tcp event support to windows Updates for ancient raspi buildchain Remove variable length assignments DNS Library Remove 2 second delay for prebuilt paths GitHub Pulse Stats for the last week: Excluding merges, 6 authors have pushed 58 commits to master and 59 commits to all branches. On master, 164 files have changed and there have been 9,708 additions and 5,240 deletions. Loki Core Enable staking in the GUI wallet https://github.com/loki-project/loki-gui/pull/52 Add an integration testing framework to Loki wallet cli and Daemon. This will make it easier to test userflows and catch bugs https://github.com/loki-project/loki/pull/312 Thanks, Kee View the full article
  6. In this update we will discuss the following: Service Nodes Whitepaper Hashing algorithm and difficulty algorithm fork Exchange Community Questions Twitter giveaway The Swap Service Nodes 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 Whitepaper 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. Exchange 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) Community Questions 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. Twitter Competition The Twitter competition winners was voted for by the public, below are the winning images First Place Second Place Third Place The Swap 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) View the full article
  7. Snider

    Response to BITKER listing concerns

    Lethean Community, We are aware that a few community members are concerned with the way that we built up hype around our BITKER exchange listing. These community members have voiced their concerns over both the listing and the validity of BITKER’s statistics. We want to clear the air about our stance, and address the concerns of our community. First, we would like to say that we are excited about being listed by BITKER, and even more excited about being listed in such a prominent exchange according to volume in the Chinese market. China has one of the largest VPN consumer rates in the world and in our eyes, this is a huge step forward. We think it is a milestone, and well-deserving of the excitement that we encouraged leading up to the exchange listing. Though being listed on an exchange in the Chinese market is an achievement for us, we are not stopping here. We are continuing to reach out to exchanges; however, when reviewing partnerships with exchanges, we strive to ensure that the exchange promotes awareness and is also fiscally viable for us to be listed on. We believe the BITKER listing aligns with our long term goal of providing VPN services to clients worldwide. This listing in an exchange located in one of the largest VPN markets will increase brand awareness and boost the amount of Lethean users. Some community members have questioned the validity of the information that was provided in our listing press release. We would like it to be known that all the details in our listing article were sourced from either BITKER directly, or from CoinGecko. One of the more prevalent criticisms that was raised is the volume of the exchange. We received all of the data referencing the exchange volume from CoinGecko. However, as an additional measure being taken to clear the air, the Lethean team has asked BITKER to respond to the concerns about volume. The specific amount of users registered on BITKER’s platform was provided to us by the BITKER team, and their launch date was sourced from their website. We can appreciate why the community has reservations about BITKER’s validity, and the fact that they are not listed on CoinMarketCap. The Lethean Team was advised by BITKER that they have requested listing on CoinMarketCap. We have asked BITKER for an official response to these matters. You can find their initial response here. We have also asked BITKER for a response addressing the amount of registered users and the amount of volume on their platform. At this time we are waiting for a reply, but we will keep you updated as we know more. In summation, we are still very excited to see what the future holds for Lethean after opening the doors to the Chinese market. Additionally, we understand the reservations that our community has about the information that was provided. We have asked BITKER to respond to these concerns. When that information becomes available, we will direct our community to the response from BITKER. Despite the questions that were raised, we will maintain our focus on future listings for our community. View the full article
  8. Snider

    Weekly update 9th of November

    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! Success! Email SUBSCRIBE! Join our Newsletter! SUBSCRIBE! You have Successfully Subscribed! Labels AirTime blockchain company mining Mobile app platform trading updates wallet The latest Weekly update 9th of November Weekly update 3rd of November Niffler.co Announces Listing Of TUBE As A Trading Pair Weekly update 26th of October Weekly update 19th of October The post Weekly update 9th of November appeared first on BitTube. View the full article
  9. Snider

    CASH, CREDIT, OR GRAFT?

    One good question that comes up often is Do people really want to pay with cryptocurrency? Some make an argument that people see cryptocurrency as a long term investment and don’t want to spend it on daily items, others say that merchants might be reluctant to accept crypto due to the regulatory uncertainty, yet other say that people are unlikely to pay with crypto due to its volatility. Truth is, they all have a point and there will be limiting factors on crypto for payment adoption (at least for some time). However! We want to point out that GRAFT’s main purpose in life is not crypto acceptance per se – but providing a decentralized credit/debit payment network alternative that doesn’t rely on issuing banks and spreads the fees across the network. Crypto acceptance makes a good first use case, but it doesn’t end there. From the user’s point of view it’s a way to have an alternative to traditional credit / debit cards with underlying privacy, reasonable rates, loyalty program consolidation, etc. Here would be a typical decision tree that a user would be facing at the check out: A community member had this to say on this topic, which is pretty on point: Firstly, Graft is not a “Crypto POS” it’s a decentralized payment network that can be used at the POS or as an online payment gateway. We don’t need the widespread adoption of Cryptocurrency as a medium of exchange for the Graft Network to be successful. For example, if the Graft Network ‘today’ was doing just 0.1% of the Visa Network’s transaction, then Graft SuperNodes would be returning close to 300% pa ( SuperNode owners would make exceptional income from SN rewards, thus the Graft price would rapidly increase). However, keep in mind that we are not just going after Visa, we are going after Mastercard, Amex, Diners, Paypal, Western Union …the list goes on. 2018 has seen a rise in the popularity of stable coins to address the volatility issue. There are now over 57 Launched or pre-launched stable coins. Because Graft is a payment Network, not just a payment processor ($GRFT coin acts like a utility token and becomes a gateway to accept other Cryptocurrencies) – so the Graft Network could, in theory, facilitate payment from any cryptocurrency, thus there’s no reason it can’t support a whole basket of stable coins (it just requires the backing of an exchange broker/ liquidity provider). There are also new gen coins coming out with Inflationary monetary policies (eg GRIN) which are designed for the purpose of becoming a medium of exchange (to mimic fiat currencies) . Soon the volatility risk or purchasing/receiving Crypto payments will be a thing of the past. Merchants will also be incentivized to receive Cryptocurrency due to lower fees…. As for consumers: A lot of people have this US/western mindset and still have lots of faith in government-backed fiat currencies. However, go ask the people of Venezuela, Argentina or Turkey how safe they feel holding their own Government backed currencies. If you look through the history of fiat currency, they always collapse/end in hyperinflation. It’s just a matter of time. Sure, widespread adoption of cryptocurrency as a medium of exchange could be years or decades away. However, as already mentioned, we don’t need widespread adoption for the Graft Network to be successful, we need less than 0.1% (between Visa/ MC/AMEX/ Dinners etc). The post CASH, CREDIT, OR GRAFT? appeared first on Graft Blockchain. View the full article
  10. Masternodes.pro listing, complete website overhaul and custom Saronite algorithm – November 9th, 2018 In today’s update we will be discussing the following topics: https://MasterNodes.pro listing and the complete website redesign of Saronite.io The Saronite team has been very busy over the past few weeks working through the process of getting listed on Masternodes.pro, completely overhauling the website and actively working on our new custom Saronite algorithm. To start, Saronite is now officially listed on MasterNodes.pro! Masternodes.pro has roughly 4.9 million views per year, 400,000 monthly and about 13,300 views per day. We believe this will drive more traffic and interest to Saronite. Which will drive more growth, more developers helping with the project and more people running service nodes. The Saronite team is also interested in getting listed on MasterNodes.online which has a comparable stats, but has a higher Alexa rank and more traffic overall. This listing will come at a later date. If you would like to check out Saronite’s MasterNodes.pro page, click here. Next on the list, the website overhaul. Saronite’s current website is very functional and provides all of the necessary information very easily. Functionality is a key part of any website, without that the website is useless. The current site does this well. However, the visual aspect of the website is a bit rough around the edges. If you have visited the site more recently, you may have noticed some smaller changes such as: the new social sidebar, our new logo animation, the primary menu system has been reworded & reworked, a new pre-loader and page transition effect. These are site wide changes that cannot be hidden while the new homepage was being redesigned. Overall, the new website should be just as functional if not more so, and be much more visually appealing. (For the full visual experience I recommend using Chrome or Opera while browsing Saronite.io) We are excited about the future of Saronite and have made significant progress over a short period of time. We will continue to put one foot steadily in front of the other, join us on this adventure. View the full article
  11. Snider

    The State of Private Messaging Applications

    Over the course of this article I will analyse three key elements which all messenger applications must consider. Metadata: Any information, aside from the actual message, which is transmitted and can be exposed to third parties. Encryption: How your messages are encoded to obfuscate their content. Scalability and Attacks: How well the messenger responds to increases in usage and if there are any known attack vectors or exploits to the specific system. I will also explore how centralisation/decentralisation can affect the privacy and security of each element. Centralisation, in this context, refers to whether the messenger architecture has a group of permissioned non federated servers, which are the sole servers and can hold or relay messages. Through these lenses, I will examine the most popular messaging services which claim to be encrypted, or private, along with Loki messenger. Centralised server models, like Telegram, Facebook Messenger, Signal, Whatsapp or XMPP (Federated) Decentralised messengers like Tox and Bitmessage Mixnet based messengers like Loki Messenger Metadata Think about it like this: if I send a letter by post to my friend, I will put their full name and address on the front, and my full name and address on the back so that I can receive a reply. Although no one can see inside my letter and read its contents, the postal service now has a good idea of who I am, who I sent my letter to, and what time I sent my letter. This information is typically referred to as metadata. Here’s a great quote from Kurt Opsahl from the EFF, writing on the topic of government metadata collection: “They know you rang a phone sex service at 2:24 am and spoke for 18 minutes. But they don’t know what you talked about. They know you called the suicide prevention hotline from the Golden Gate Bridge. But the topic of the call remains a secret. They know you spoke with a HIV testing service, then your doctor, then your health insurance company in the same hour. But they don’t know what was discussed.” [1] And Michael Hayden (former Director of the NSA) “We kill people based on metadata” [2] Now how does this relate to private messaging? Centralised services When you use a service like Whatsapp, Telegram or Signal, you connect directly to a server owned by one of these companies. When you send a message, you must somehow tell that centralised server who you are and who the recipient of your message is. You will also typically give up your IP address and your phone number, depending on the client you use. These centralised services have the capacity to collect metadata. Some providers, like Whatsapp and Facebook Messenger, openly admit to collecting and storing their user’s metadata. [3][4] Some services, like Signal and Telegram, have policies against storage of user metadata. [5][6] These policies require a significant amount of trust, however it has been shown countless times that as soon as trust is involved in user privacy, companies and governments will violate that trust. Look no further than popular ‘private’ email service, Hushmail, which was compelled legally to hand over users’ private information to governments. [7] The only solution to this problem is for these centralised, privacy centric services to never have the ability to collect sensitive user data. (A note on XMPP) Messengers based on XMPP are slightly different in their construction since they operate on a federated model. [8] This means that only a protocol is provided, users/providers can operate their own servers (which means that metadata is held by individual servers), and users have more choice in the parties they trust to store their data. This is a step in the right direction, though XMPP servers can still collect this data and have the ability to transmit it to third parties. Decentralised Services So how do the decentralised models deal with metadata? Well, there’s a few out there and they each approach metadata in a different way. Services like Tox, and other P2P messengers, by their very nature do not require metadata to be stored on any centralised server, since messages are routed directly to their participants rather than traveling through servers or hopping through a mixing network. On the surface this can sound great, but really it gives more power to ISPs. Although the packets of data may be encrypted, ISPs can see the IP address of the person you are messaging, and if they can resolve the IP address of the recipient then they are able to very accurately ascertain information on who you messaged and at what time. This is something centralised services (Telegram, Signal, and WhatsApp) prevent. If encrypted properly, your ISP only knows you are communicating with a messaging service server, and never knows the actual IP address of your recipient. Bitmessage is one of the other fully decentralised messaging models and might be the next best for hiding message metadata. Bitmessage operates a floodfill network, meaning that messages aren’t directed towards specific participants like they are in most other networks. In Bitmessage, every user is distributed a copy of every encrypted message. Once a user receives a message, they must attempt to decrypt the payload. This means when I want to send a message, I “flood” the message to the peers I know, who then flood the message to the peers they know. This technique makes it difficult to ascertain whether a user is merely relaying a message, or if they are the source of the message. It is also imposible to ascertain whom the true recipient is, as all clients receive all messages and attempt to decrypt them. However, there are significant downsides to operating floodfill networks, such as the high bandwidth consumption and computational overhead of attempting to decrypt each message you receive. Loki Messenger Loki Messenger uses a number of different techniques for obfuscating metadata. In the context of the above, it is close to a mashup of Bitmessage and the Tor network. Like Bitmessage, Loki Messenger uses a decentralised set of nodes (Service Nodes) to relay messages to other users. Service Nodes are incentivised by the Loki blockchain and undertake the job of relaying messages to receive a small reward in cryptocurrency. To avoid metadata collection in both offline and online communications, a method called onion routing is employed. Onion routing in Loki positions a set of randomly selected (simplified) Service Nodes between the user and the destination of their message. As the message hops through each Service Node toward the final recipient, a layer of encryption is removed. This onion routing provides a number of protections: In a typical connection it is not possible for a single Service Node to gather enough metadata to form a connection between the sender and receiver of a message. Service Nodes are run by the community, and are globally distributed, which makes targeted legal action difficult. Service Nodes require a large amount of the Loki cryptocurrency, meaning they are staked into the system. Any actions which reduce the usefulness of the Loki Messenger will likely also reduce the value of the Loki cryptocurrency. This financially incentivises good behaviour. When a direct link between users cannot be established (the recipient is offline), Loki can also enable metadata protection for offline messages. This is done through a process called Swarm messaging. Each Loki Messenger user resides in a swarm of 10 Service Nodes. To contact another user, I can use their public key to figure out their swarm identity. My message is then sent to one of the ten nodes in their swarm, which will flood the message to the 9 others. When the user comes online, they will randomly query a node in their swarm. If that Service Node is holding a message for them, the user will download it directly from the Service Node. Alice sends a message to Bob, Bob’s assigned Swarm is B, When Bob comes online, he queries a random node in his swarm and receives Alice’s message. Encryption Encryption refers to the methods each messenger uses to obfuscate the actual data inside a message. It’s easy to think of encryption as an on/off switch, but in actuality encryption is more like a volume knob – there are various features and implementation details which can marginally increase or decrease the security of the encryption in an app. Centralised services There is significant variance when it comes to how Telegram, Whatsapp, Signal and Facebook Messenger deal with encryption – with some services providing strong, mandatory and auditable encryption, and others providing much weaker protections. Signal Signal is widely considered to be the best private messaging app when it comes to encryption standards as all Signal conversions are end to end encrypted by default. Signal uses the aptly named Signal protocol, which is developed as an open source project by Open Whisper Systems. [9][10] The Signal protocol has also undergone a security audit, and the results were generally positive finding only minor vulnerabilities. [11] When correctly implemented, the Signal protocol maintains both Perfect Forward Secrecy (PFS) and Deniable Authentication (DA) in both synchronous (online) and asynchronous (offline) messages. Signal also applies encryption automatically to group chats. PFS is the ability for a protocol to tolerate the loss of a private key, without compromising the privacy of other encrypted messages that are not part of the exposed session key. DA is the ability for each party to prove to themselves that a message was signed by the other participant, but can also deny this fact to a third party. The combination of both properties allows for a messenger where messages are end to end encrypted, selective key loss is tolerable, and the origin of sent messages can never be proven to any party other than the desired recipient. These are very strong guarantees, which in essence emulate the properties of a real world conversation. Hence, a messenger with both these properties is typically referred to as an Off The Record (OTR) messenger. WhatsApp WhatsApp provides end to end encryption on all messages by default (including group chats), and it uses the Signal protocol for its encryption. WhatsApp also maintains a public partnership with Open Whisper Systems, who assisted them in their implementation of the Signal protocol. [12] However, WhatsApp is not open source, which means there must be a degree of trust that WhatsApp’s implementation of the Signal protocol doesn’t expose vulnerabilities. Telegram Telegram provides end to end encryption, but only does so for ‘secret chats.’ These chats are opt in, which means usage is low. Telegram does not yet support encrypted group chats. For the encryption of its secret chats, Telegram currently uses the MTProto 2.0 protocol, which provides both PFS and DA. The MTProto protocol is a unique protocol, and like Signal, MTProto 1.0 has undergone formal security audits. Though in the case of MTProto 1.0, it was found that MTProto: “is not IND-CCA secure, since it is possible to turn any ciphertext into a different ciphertext that decrypts to the same message.” [13] With researchers also mentioning that “The take-home message (once again) is that well-studied, provably secure encryption schemes that achieve strong definitions of security (e.g., authenticated-encryption) are to be preferred to home-brewed encryption schemes.” [14] Since this audit, Telegram has overhauled its MTProto protocol and released version 2.0, which addresses many of the concerns that were raised in the independent security audits. [15] However many have lost trust in MTProto’s security guarantees based on the aforementioned attacks. Facebook Messenger Facebook Messenger provides two person end to end encrypted chats, but like Telegram, this encryption is only offered in ‘secret conversations’ and are opt in, meaning that the majority of users are left unprotected. For encryption, Facebook uses the Signal protocol, similar to WhatsApp (owned by Facebook), and is not open source meaning it is difficult for users to verify Facebook’s claims beyond assurances from Open Whisper Systems that the “integration was done appropriately.” [16] Decentralised services Tox Tox provides end to end encryption by default on all chats (including group chats). Tox clients all implement the Tox protocol, which uses libsodiums crypto_box implementation. Tox provides PFS and DA for all messages (other than friend requests), however Tox does not support the sending of offline messages. [17] Tox has not undergone a security audit and has come under less cryptographic scrutiny, compared to centralised messengers, due to its smaller user base. Bitmessage Bitmessage’s encryption is the most basic of the available decentralised messengers. This is mainly due to its asynchronous (offline) operation. Bitmessage encrypts only for longterm public key/private key pairs, meaning that it does not maintain PFS or DA. Bitmessage has not undergone a formal security audit, though community members expressed concern around some of the design decisions, which led to updated designs being released. [18] XMPP Since XMPP is simply a protocol, it does not enforce any type of message encryption. Though there are a number of plugins for XMPP servers and clients to enable OTR messaging, like Pidgin’s OTR, and OMEMO extensions. [19] Loki Messenger Loki Messenger is a fork of the Signal messenger, which means Loki Messenger fully implements the Signal protocol and maintains all the properties of OTR. All Loki Messenger code is open source, allowing users and auditors to ensure the viability of our implementation. [20] There are a number of differences between Loki Messenger and Signal messenger, though encryption wise the only major difference is the storage of pre keys, which in the case of Loki Messenger does not occur on a set of centralised servers, but as the result of prekeys being passed as extra data in message payloads. Scalability and Attacks Although there are effective methods for relaying messages across infrastructure that is being passively surveilled, these methods often present a clear trade-off to the end user or relay operators; an increase in bandwidth, or processing power for a increase in privacy. In addition, we should consider specific attacks that can be effective against both centralised and decentralised architectures. Centralised Services Established centralised messaging services like Signal, Telegram, and WhatsApp all have frameworks which enable them to scale with their users. Because they make no overt attempt to obfuscate metadata on a protocol level, their servers can simply relay messages from the source directly to the destination – this level of activity has low overheads. Centralised server models also have an easier time dealing with spam, since they can (and do) impose identity thresholds. These thresholds commonly require a user to sign up to their service using a valid mobile phone number. This limits the number of fake accounts a malicious actor can create. However, this type of centralisation can also present significant problems. Primarily, these services become centralised points of data collection, meaning they can expose themselves to requests from law enforcement or face legal action for activity that is occurring on their platforms. It also creates a honeypot for hackers seeking to obtain sensitive information. Additionally, most of these messengers are free to use, which means they need alternative means to pay for the infrastructure costs and staff. In order to create a viable business model, these businesses often attempt to montiese their user base by selling user data to advertisers. Decentralised Services Decentralised services primarily suffer attacks related to their inability to associate a physical identity with each one of their virtual users. This makes many decentralised models vulnerable to Sybil attacks, which can manifest as denial of service attacks or attacks that are used to passively surveil the network. In particular services, like Bitmessage, which maintain no concept of a trusted authority, an attacker can generally operate a large portion of the client architecture and pretend to be many legitimate users. In this instance, the attacker could attempt to flood a large number of messages into the system inundating its network. Bitmessage has provided a solution to this through a small proof of work which is generated for each message sent, making it prohibitively costly for an attacker to spam thousands of messages using numerous fake identities. A separate kind of Sybil attack can target network routing architecture. As there is a relatively low cost to running this architecture, operating a majority of the routers in the network can enable passive temporal analysis. In Tox, this can lead to flooding the DHT (a distributed table which holds the state of the network) with malicious nodes which can then segment users, cause denial of service to the ‘real’ Tox network, or even errode the effectiveness of the onion routing that Tox uses to update its DHT. [21][22] Loki Messenger Loki introduces proof-of-work (PoW) on messages that are stored offline. Depending on the Time To Live (TTL) on the message, the difficulty of the PoW is adujsted to be easier or more difficult. For messages that do not require storage, there is no PoW needed as the overhead of processing these messages on Service Nodes is relatively low. Loki Messenger is able to reduce the impact of Sybil attacks on the routing architecture by requiring that each Service Node lock a large amount of Loki in a special time-locked transaction. This creates an inherent market-based Sybil resistance, making it prohibitively expensive for any single actor to own a large enough number of nodes to perform effective temporal analysis. [23] Additionally, requiring that each Service Node stake an amount of Loki makes enforcement of good behaviour much easier. If a Service Node is acting poorly, then their stake will remain frozen and they will not receive any rewards for their staking period. This negative consequence (loss of opportunity cost) constitutes a programmatically self-policed punishment system which is run by the Service Nodes themselves in a system called ‘swarm flagging.’ [24] Summary The messenger landscape is full of emerging and established projects. It is important for consumers to critically analyse each messenger against key metadata, encryption, and scalability/attack resistant criteria. Although some messengers may provide strong encryption, they may not protect users’ metadata. As data breaches on centralised services continue, consumers are calling for more privacy centric applications. As the decentralised ecosystem grows, centralised services like WhatsApp, Signal and Telegram will have to compete against decentralised or federated alternatives. Ultimately, the service which maintains the highest privacy and best user experience is likely to be the winner of this battle. References [1] “Why Metadata Matters | Electronic Frontier Foundation.” 7 Jun. 2013, https://www.eff.org/deeplinks/2013/06/why-metadata-matters. Accessed 10 Sep. 2018. [2] “Former NSA boss: “We kill people based on metadata”” https://youtu.be/UdQiz0Vavmc?t=27s Accessed 10 Sep. 2018. [3] “WhatsApp security and role of metadata in preserving privacy, https://arxiv.org/ftp/arxiv/papers/1701/1701.06817.pdf. Accessed 5 Jul. 2018. [4] “Facebook scraped call, text message data for years … – Ars Technica.” 24 Mar. 2018, https://arstechnica.com/information-technology/2018/03/facebook-scraped-call-text-message-data-for-years-from-android-phones/. Accessed 5 Jul. 2018. [5] “Battle of the Secure Messaging Apps: How Signal Beats WhatsApp.” https://theintercept.com/2016/06/22/battle-of-the-secure-messaging-apps-how-signal-beats-whatsapp/. Accessed 10 Sep. 2018. [6] “Telegram Privacy Policy – Telegram Messenger.” https://telegram.org/privacy. Accessed 10 Sep. 2018. [7] “Hushmail warns users over law enforcement backdoor • The Register.” 20 Nov. 2007, https://www.theregister.co.uk/2007/11/20/hushmail_update/. Accessed 10 Sep. 2018. [8] “XMPP | XMPP Main.” https://xmpp.org/. Accessed 11 Sep. 2018. [9] “GitHub – signalapp/libsignal-protocol-c: Signal Protocol C Library.” https://github.com/signalapp/libsignal-protocol-c. Accessed 11 Sep. 2018. [10] “Open Whisper Systems – Wikipedia.” https://en.wikipedia.org/wiki/Open_Whisper_Systems. Accessed 11 Sep. 2018. [11] “A Formal Security Analysis of the Signal Messaging Protocol.” 27 Oct. 2016, https://eprint.iacr.org/2016/1013.pdf. Accessed 11 Sep. 2018. [12] “Signal >> Blog >> Open Whisper Systems partners with WhatsApp to ….” 18 Nov. 2014, https://signal.org/blog/whatsapp/. Accessed 12 Sep. 2018. [13] “On the CCA (in)security of MTProto – Cryptology ePrint Archive.” https://eprint.iacr.org/2015/1177.pdf. Accessed 12 Sep. 2018. [14] “On the CCA (in)security of MTProto – Cryptology ePrint Archive.” https://eprint.iacr.org/2015/1177.pdf. Accessed 12 Sep. 2018. [15] “MTProto Mobile Protocol – Telegram APIs.” https://core.telegram.org/mtproto. Accessed 12 Sep. 2018. [16] “Signal >> Blog >> Facebook Messenger deploys Signal Protocol for ….” 8 Jul. 2016, https://signal.org/blog/facebook-messenger/. Accessed 12 Sep. 2018. [17] “otr-like offline messages · Issue #1432 · irungentoo/toxcore · GitHub.” https://github.com/irungentoo/toxcore/issues/1432. Accessed 13 Sep. 2018. [18] “My Security Analysis of Bitmessage.” 20 May. 2013, https://bitmessage.org/forum/index.php?topic=1666.0. Accessed 13 Sep. 2018. [19] “#16801 (Add OMEMO Encryption support to XMPP) – Pidgin.” 10 Feb. 2011, https://developer.pidgin.im/ticket/16801. Accessed 13 Sep. 2018. [20] “GitHub – loki-project/loki-messenger: Signal — Private Messenger for ….” 24 Aug. 2018, https://github.com/loki-project/loki-messenger. Accessed 13 Sep. 2018. [21] “Tox should be resilient to Sybil attack. · Issue #517 · TokTok/c-toxcore ….” https://github.com/TokTok/c-toxcore/issues/517. Accessed 14 Sep. 2018. [22] “GitHub – irungentoo/toxcore: Tox Onion routing spec..” https://github.com/irungentoo/toxcore/blob/5ea703c844b12e86702c35b53b0b798fe5f86634/docs/Prevent_Tracking.txt Accessed 14 Sep. 2018. [23] “Cryptoeconomics of the Loki network.” 11 Jul. 2018, https://loki.network/Cryptoeconomics. Accessed 14 Sep. 2018. [24] “White Paper – Loki Network.” 13 Jul. 2018, https://loki.network/wp-content/uploads/2018/08/LokiWhitepaperV3_1.pdf. Accessed 14 Sep. 2018. View the full article
  12. Dear Lethean community, In the near future, Lethean tokens will become transferable. While this is cause for celebration — we have, together, reached an important milestone — it is also a time to remind everyone of the immense number of criminals who try to steal people’s cryptocurrency and of the many scams that they perpetrate in order to do so. Please, keep your Lethean safe. While there is no substitute for consulting with an information security professional about the particulars of your own environment and situation to ensure that you properly protect your cryptocurrency holdings, there are some general pieces of information that we thought were important to mention. Be vigilant when interacting with Lethean on social media. It is likely that criminals will create fake Twitter, Facebook, Telegram, Discord, and other accounts that attempt to impersonate Lethean and/or members of its team. They may use the bogus accounts for all sorts of nefarious purposes. Do not let them trick you. Lethean’s real accounts are listed on our website https://lethean.io — so, please, do not follow any accounts claiming to be Lethean that are not listed there — and, definitely, DO NOT follow any instructions provided by any potential impersonators. Beware: Many impersonators use account names that are similar to real accounts — our real account on Twitter, for example, is @LetheanVPN; scammers are likely to try using account names that are similar — @LetheenVPN, @LetheanUPN, @LethaenVPN, etc. Remember: Large amounts of money have been lost by people falling prey to such scams — do not join that crowd. Never send your wallet, private keys, mnemonic seed, or any cryptocurrency of any kind to anyone from Lethean in exchange for assistance. We will never ask you to send us any compensation in exchange for help, and will never ask you to send any cryptocurrency in order to participate in a giveaway. By, never, we mean never. Confirm addresses. Before sending cryptocurrency to Lethean for the purchase of Lethean tokens or some other legitimate reason, always confirm that the address to which you are sending your money matches the address listed on our website. Of course, “matches” means matches exactly. It is also a good idea to call or email us before sending any cryptocurrency to us. Use only official versions of Lethean. Cryptocurrency thieves often attempt to install, or trick others into installing onto their electronic devices, malicious software that attempts to steal cryptocurrency wallets or keys from infected machines. Sometimes the malicious software even masquerades as official software from a provider. As such, there may be attempts by criminals to create and disseminate fake Lethean software that is infected with malware. Therefore, download Lethean software from only our official Github repository https://github.com/LetheanMovement or from our website — not from anywhere else. All files that you download should be verified for authenticity and accuracy by comparing the hashes generated by a SHA256 tool. Run on the downloaded files with the expected values that are listed on our website. Do not use hash value lists from any third-party site to check the accuracy of Lethean files. Secure your devices. Make sure that you are using Internet security software on any and all computers, smartphones, and tablets from which you plan to access Lethean software and/or tokens. If for some reason Internet Security software flags your copy of Lethean as a dangerous application, contact us before proceeding. Sometimes, anti-virus software sets off false red flags, but, sometimes, it catches malware that has somehow infected an application after it was downloaded to your device. This email is meant to provide some tips, but, obviously, does not contain a comprehensive guide to cryptocurrency. For further reading we suggest seeing the following articles: 18 Tips to Help You Secure Your Cryptocurrency How To Keep Your Bitcoin Safe And Secure This is how you can protect your cryptocurrencies from hackers Securing Your Wallet How to Prevent Your Bitcoins from Being Hacked or Stolen Beware: Criminals Are Sending Extremely Well-Written Fraudulent Emails Related To ICOs And Other Cryptocurrency Investment Opportunities Scam Alert: Beware Social Media Accounts Impersonating Cryptocurrency Firms and Figures We hope that this announcement helps you to keep your assets safe in these times of growth. If you have any questions or need any assistance, you are always welcome to reach out to us on our socials listed on our website. We wish you luck in staying safe as Lethean progresses. The Lethean team. View the full article
  13. Snider

    Bitker Exchange Listing

    BITKER As the title of this article shows, we have momentous news today! We are happy to announce that Lethean has officially been approved for listing on a new exchange, BITKER. But what is BITKER, exactly? BITKER is a major world exchange located in Singapore, but operating out of China. They have more than 300,000 registered users; this large user base is responsible for their significant daily trading volume. CoinGecko frequently ranks BITKER in the top 20 exchanges in the world by volume, and they recently reached as high as number 7. You can review BITKER on CoinGecko here. Furthermore, Bitker management has informed us that they are currently in the process of being added to CoinMarketCap. BITKER is also a one-stop digital asset trading platform which supports over the counter and margin trading. BITKER is rapidly growing and expanding its reach worldwide. We are very excited to be listed on such a reputable and high volume exchange. We hope that this listing helps our community to more easily trade Lethean in the near future. Most importantly, the BITKER listing will allow us to breach the Great Firewall of China, and it will allow us direct access to Chinese clientele who likely already use or have knowledge of VPNs. Furthermore, Chinese retail investors will be able to purchase Lethean, which offers us more opportunities relating to Chinese communities in general. To support our incoming Chinese clientele, we are currently in the process of adding a Chinese translation to our website to make it easier for Chinese people to learn about Lethean. We plan to use this strategic partnership as a launchpad to propel the Lethean brand into the forefront of the VPN market. Starting at 02:00 UTC on November 10th, users may deposit LTHN into their BITKER accounts. For security reasons, 200 confirmations will be required before deposits are credited to users’ accounts. 12 hours after deposits are opened (November 10th at 14:00 UTC), trading will begin with the following pairs: LTHN/BTC LTHN/ETH LTHN/USDT Our community can easily contact BITKER on the following platforms: BITKER Website: www.bitker.com Telegram (English): https://t.me/BITKER_oversea Telegram (Chinese): https://t.me/bitker_cn Twitter: https://twitter.com/Bitker1 WeChat: bitkerservice Riddles Over the past few weeks, we have been putting out riddles for the community to solve regarding hints towards some upcoming news. We are glad to announce that in fact, this was the news that the riddles were hinting towards. The first riddle was a magic eye puzzle, which when ‘solved’, showed the letter “B” — this stood for BITKER. The second riddle was a word puzzle where one had to find what letters were in one word of a given two, but not the other. When solved, it gave the phrase “THREE HUNDRED”, which refers to BITKER’s trading volume on the date the riddle was posted. The third riddle was a multi-step riddle involving ciphers and decryption work, even involving stenography at one point. The final answer unscrambled to “Goniurosaurus hainanensis”, which is a species of Chinese cave gecko, hinting at both BITKER’s nationality and its listing on CoinGecko. We hope users had as much fun solving the riddles to decipher the hints as we did making them. We are currently running a final puzzle with a 50K Lethean reward. If you would like to participate, please join our Discord. View the full article
  14. Creating a cronjob to auto check if service node is running. Firstly, I would like to reiterate the importance of chosing a high quality reliable VPS provider. Running the server daemon off of a home computer, or any computer / network that is not 99.9% stable presents problems. We highly discourage you from running the server daemon on an unreliable computer – If your home computer turns off, disconnects, reboots, etc, most likely your XRN will be locked for the remainder of your staking period. (< 30 days) If you are reading this and have the server daemon on a home pc, stop right now. Go purchase a reliable VPS and redeploy the server daemon. Quick Notes before starting. My VPS is running: Linux 4.16.14-feral x86_64 Use terminal command “pwd” to determine direct path. Use terminal command “ps x” to show running procs, to kill a process type “kill” and then it’s process ID “kill 33333”. Use terminal command CTRL + X to save nano files, or other information. PS; Through this guide I will be replacing certain pieces of information for security purposes, typically my username for my server. What needs to happen. Here’s what needs to happen in order for this automated process: 1:) You must create a script to run screen + saronited —service-node 2:) You must create a “job” to run to check to see if “saronited” is running. “saronited” is the identifer we are going to attach to the “screen” and it will be an automated process which will run the server daemon; AKA “saronited –service-node” AKA the important part of your server In this example, I am using the VPS provider FeralHosting.com – some variables may be different according to your vps host. I have had 100% uptime with FeralHosting, just saying. PART 1 – SCRIPT CREATION Firstly, log into your VPS and type “ls” this will print your current (typically home) directory. The name of the script we’re going to create is “saroscript” (our script we’re going to make for our autoamted cron job) in the base directory (( AKA ~/ (short key to get to your base dir is “cd ~/” )) Once in a directory where you can create files, lets say your home directory, type “nano saroscript.sh” (You may be prompted to select a text editor, I use Nano) Once inside your new “saroscript.sh” get ready to paste the text below. BUT FIRST, you need to correct the location to the full path. This information can be obtained by typing from the terminal command “pwd”. My example is on Pastebin at the link below, you will have to adjust it accordingly. Example is here: https://pastebin.com/TDmukUPr Once you’ve made the nesscary changes hold CTRL + X -then hit “y” to save your nano document. After saving your new script, run this command in the directory where you created the script: chmod 700 ~/saroscript.sh This script is basically first a check (which is indicated by [[ ]] – It’s say “Check if “saronited” is running, if no then run the next line : screen -dmS saronited — /media/md1/YOURUSERNAMEHERE/saronite-linux-64-v1.1.1.0/saronited –service-node The script above firstly runs “screen” (as you learned from the node setup guide screen creates a detached screen that will run in the background.) The script then gives the “screen” a name of “saronited” and then it calls this path /media/md1/YOURUSERNAMEHERE/saronite-linux-64-v1.1.1.0/saronited –service-node (which if everything works, should turn on your service node) Before moving forward, I would test this script by simply typing “./saroscript.sh” in the directory it’s located. For our example the dir it will run out of it is your home dir (~/ ) “/media/md1/YOURHOMEDIRECTORY” – – – Assuming your service node daemon (saronited –service-node) it not already running, it should start in a detached screen. If it’s already running, you will get something like “+++ whoami ++ pgrep -fu YOURUSERNAME saronited + [[ -n 38333 ]]” Which means the script found “saronited” (or a similar process) already running as process ID 38333. (optional) To list all detached screens type “screen -ls”. To switch to a running an already running “screen” type screen -x 36234 (<- this would be your PID number, not necessarily 36234 If you want to kill a screen process, type “ps x” then “kill yourprocessid here”. PART 2 – CRONJOB CREATION OKAY! Now you have created the script, and you know how to move between screens and understand the context of the situation lets move to creating the cronjob. In any area in linux, type “crontab -e“ You should be presented with a window with some marked out content indicated by ### symbols. Ignore these. Arrow down to an area with no # symbols. Get ready to copy and paste this, but before you do, you need to adjust it accordingly. Example is between dashed lines. Pastebin here: https://pastebin.com/7hM7beBP ———— */5 * * * * /media/md1/YOURUSERNAME/saroscript.sh >/media/md1/YOURUSERNAME/saroscript.sh.cronoutput 2>&1 ———— Remember what we did earlier? Correcting the direct path? We have to do that again. Remember, command “PWD” gives you the full path of your current terminal location. Also recall that I created my “saroscript.sh” in my home directory of “media/md1/YOURUSERNAME” – – – Once everything is correct, hold CTRL + X then hit “y” to save your cronjob. The above cronjob runs our “saroscript.sh” every 5 minutes. If the script detects that a process or screen is already running with the name “saronited” you will get a message like so: “+++ whoami ++ pgrep -fu YOURUSERNAME saronited + [[ -n 38333 ]]” If you would like to see the most recent log output of your cronjob, simply browse to the location your created your “saroscript” probably in your home dir “cd ~/”, type “ls” and you’ll see “saroscript.sh.cronoutput” – type “nano saroscript.sh.cronoutput” to see log. If the server reboots, or loses power, the cronjob will automatically start within 5 minutes of the server booting up, it will check if screen / process “saronited” is running, when it detects it isn’t it will create a new screen and run the script “saroscript.sh” which will then run this command “/media/md1/YOURUSERNAMEHERE/saronite-linux-64-v1.1.1.0/saronited –service-node” which will start your service node If you have questions or spotted an error in this guide feel free to ping mFridge_ on Discord. View the full article
  15. Snider

    Weekly Dev Update #21

    Hey Y’all, Some bigger changes going in this week as we prepare for our next hardfork, the date of which should be announced soon so watch out for updates in the community channels! Loki Core Change governance wallet reward from per block to once every 5040 blocks (one week). This reduces blockchain bloat and makes the governance wallet more manageable, 5% amount stays the same, (this will require a hardfork to take effect) https://github.com/loki-project/loki/pull/303 Merge upstream again, keeping up to date with bug fixes that were released after bulletproofs release https://github.com/loki-project/loki/pull/304 Differentiate coinbase, service-node, governance and miner rewards in the CLI wallet https://github.com/loki-project/loki/pull/306 LLARP / Lokinet We welcome our new full-time Lokinet developer, Michael https://github.com/mt2309. He started by cleaning up our CMakefile – you will see more commits from him over the coming weeks Progress continues on libllarp Support older versions of rapidjson Make jsonrpc server build optional More event loop TCP support Fix timers to use less energy for better laptop support Establish a max ev write buffer Static analysis clean up Call DHT clean up timer Flush kqueue on tick Give HS look up 20s instead of 10s FreeBSD build instruction sh support for bootstrap FreeBSD: add route, disable special tun behaviour Man page updates Modenise CMake build, now requires 3.7 Dtrace profiler start Use event loop for time Recuse Windows files from old builder repo Added intel intrinsics for 32bit AVX Clean up a lot of MSVC compiler support Refactor Windows event loop and got it working correctly DNS library Static analysis fixes MX and TXT record support GitHub Pulse Stats for the last week: Excluding merges, 4 authors have pushed 57 commits to master and 58 commits to all branches. On master, 121 files have changed and there have been 17,151 additions and 993 deletions. Most changes can be found at: https://github.com/loki-project/loki-network/ Current version: v0.3.0 https://github.com/loki-project/loki-network/releases/tag/v0.3.0 Loki Messenger Add message storage server repo, this will be run on service nodes to store messages offline as per their TTL for Loki Messenger https://github.com/loki-project/loki-storage-server Bug fixes for PoW calculation in Loki Messenger client https://github.com/loki-project/loki-messenger/pull/21 Add dropdown list for Mnemonic language selection https://github.com/loki-project/loki-messenger/pull/22 Add server side PoW validation https://github.com/loki-project/loki-storage-server/pull/2 Thanks, Kee View the full article
×