BOScoin [BOS] | A congressional cryptocurrency platform for trust contracts



  • BOScoin Fundraiser Starts Now!

    BOScoin: Self-Evolving Cryptocurrency Platform

    The BOScoin Fundraiser Event has officially started! The Fundraiser starts from May 10th, 2017 (GMT) and ends on June 20th, 2017 (lasts for 41 days).

    Overall 276,093,688.786 BOScoins will be distributed. The exchange rate is 1 Bitcoin = 40,000 BOScoin.

    We only accept Bitcoin. The minimum contribution amount is 0.01 BTC. The maximum contribution amount is 300 BTC.

    When participating in the BOScoin Fundraiser you’re agreeing to the Terms and Conditions.

    Join the BOScoin Fundraiser by registering at the link below. https://boscoin.io/member/join/?lang=en

    If you’re not sure how to participate in the BOScoin Fundraiser, please talk to our customer support team via the chatting widget (bottom-right corner) on the BOScoin website (https://boscoin.io).

    Learn More About BOScoin — https://boscoin.io



  • BOScoin [BOS] Bounty Updated on Dashboard

    BOScoin: Self-Evolving Cryptocurrency

    The Bounty Tracker has been updated! You can now check how much bounty you earned in your BOScoin Dashboard. Login to confirm your Bounty.

    The Bounty Program started on March 28, 2017 and ended on May 10, 2017 (for 44 days). Overall, there were 9,311 Bounty applications.

    You can check your Bounty in the “Additional Transaction History” section near the bottom of the Dashboard.













  • BOScoin - BOS Platform Revised Plan!

    We appreciated everyone’s continued interest in the BOS Platform and would like to share with you what we have done up to now, and also the plans for the future.








    Below will provide a breakdown of the milestones with more information, however we acknowledge the current plan has deviated from previous plans to release the Genesis Block without the simple Trust Contracts functionality in October, and we have genuine reasons we believe the new approach will benefit the platform as further explained below.

    Up to now, we have believe it is best to walk before you run; especially with a technology with so much uncertainty (although the Bitcoin whitepaper was released in 2008, the technology is still under constant improvement as evident from all the BIPs, especially the current BIP148 with so much uncertainty).

    Stellar’s FBA consensus protocol benefits from the unique quorum consensus approach. The stability of the network may depend on the configuration of the quorums — whereby some cases, the entire network may be out of sync or in worst cases, operating in their own silos.

    For our BOS Platform, we believe a structured quorum configuration will add to the performance and reliability of the Platform and have planned according to this. Due to the new concepts in this space causing uncertainty, we have decided to initially release the Platform in C++, testing various aspects (security, performance, reliability, agility), but also focusing the understanding on how quorum configurations will affect the network as a whole — whereby later we will move to a D language-based Platform to further the performance of the platform (don’t fear, we have a team currently working on the D Platform!). We have also taken into consideration the high interest of the community wanting to use the Platform, and wish this path of development satisfies the general community.

    In parallel to protocol development, we have also identified and will conduct a project setting up a global community supporting the BOS Platform; this will have strong correlation to the quorum aspect of the Platform, and also the betterment of the token in general.

    Although touched on in the above paragraphs, we aim to provide more information on the effect of quorum configurations in a later article — and we aim to have that sooner rather than later. In the meantime, please refer to a our draft concept of the community building piece here:

    20170726 Global BOS Community Network [DRAFT]
    Global BOS Community Network DRAFTdocs.google.com

    Private TestNet

    The first of the major development milestones is the Private TestNet, which is in preparation of the BOS Platform TokenNet to be launched by end-September 2017. Testing of the BOS Platform commenced internally within the BOS team on July 25th, 2017 and will run for 5 weeks. It will test the Platform, the FBA Stellar Consensus Protocol written in C++.

    There are 3 main categories of focus for the test: performance, security and of course quorum configuration, where all tests will be conducted by code. Below provides more detail in the actual testing parameters:

    General Protocol Performance:

    • Network latency based on quorums in different regions
    • Different transaction amounts
    • Different transaction values
    • The latency, collision and error rates
    • Network stress testing (consensus algorithm, transaction amounts, transaction values)
    • Horizon server capacity

    (Horizon is an API server for the Stellar ecosystem. It acts as the interface between stellar-core and applications that want to access the network)

    Security:

    • (We are currently engaging in a security consultancy for this aspect)

    Quorum Configuration:

    • A network with: Basic 1 quorum with 4 nodes 1 Horizon server
    • A network with: 2 quorums in separate regions, consisting of 10 nodes each & Horizon server
    • A network with: 2 quorums in separate regions, consisting of 50 nodes each & Horizon server
    • A network with: 2 quorums in separate regions, consisting of 100 nodes each & Horizon server
    • A network with: 3 quorums in separate regions, consisting of 10 nodes each & Horizon server
    • A network with: 3 quorums in separate regions, consisting of 50 nodes each & Horizon server
    • A network with: 3 quorums in separate regions, consisting of 100 nodes each & Horizon server
    • A network with: 3 quorums in separate regions, consisting of different number of nodes per quorum & Horizon server
    • Note: We will use Amazon Web Servers located in different regions globally to conduct the testing

    Screenshot of Private TestNet

    Public TestNet

    The Public TestNet allows for the general public to participate in the testing of the BOS Platform. This test will follow the same structure as the Private TestNet above.

    Public TestNet is scheduled to commence by the end of August and will run for 4 weeks. We will provide more details on this as the date approaches, including how to participate and how to actually test the Platform — Please keep an eye out for the communications.

    BOS Platform TokenNet

    The BOS Platform TokenNet is scheduled to launch end of September 2017.

    Alpha TokenNet aims to release the Platform in C++, a web-wallet, and have the BOS Platform on exchanges. We hope that the community will enjoy the freedom of moving completing transactions within the Platform and also exchange with external crypto-tokens.

    There will be associated communications leading up to this milestone including more walkthroughs on how to run nodes, use the wallet, and etc.

    Genesis TestNet

    The Genesis TestNet will aim to test the Genesis BOS Platform, this is planned for mid-December.

    Please read ahead to understand what the Genesis BOS Platform will deliver.

    Genesis BOS Platform

    The Genesis BOS Platform will be the release of the BOS Platform using the Stellar Consensus Protocol written in D, and all run off the BOS Platform’s Trust Contact. We will also be releasing:

    • Trust Contracts
    • mFBA Consensus Protocol in D
    • Congress Budget
    • Transaction Fees
    • Freezing Rewards
    • Block Confirmation Rewards
    • Mobile Wallet

    Genesis BOS Platform is targeting to be released in the beginning of 2018.

    Nebula BOS Platform

    In the not too distant future, we aim to deliver the Nebula BOS Platform, which will include everything in the Genesis Platform, including Proposals and the final Congress Network, and the Self-Evolving Governance System.

    Applications

    Supporting applications are also in development and more information will be provided later.

    We hope this paints a picture of the path ahead for the BOS Platform for you and would like to reiterate our appreciation for your continued interest and support. We will be in contact soon about the community building activity and other information (and we will!); however in the meantime, please feel free to pop into our slack to bounce healthy conversations with us.




  • Thanks for the info



  • BOScoin [BOS] - Smart Contracts & Trust Contracts — Part 1

    {Pre-word: This article has been split into 3 due to the length and ongoing research into smart contracts. Part 1 will look into a general understanding of what smart contracts are and how other blockchain projects have incorporated into their design, Part 2 will look into BOS Platform’s Trust Contracts, and Part 3 will aim to provide some analysis on the design differences}

    BACKGROUND

    Smart Contracts in General

    The concept of smart contracts was introduced by Nick Szabo mid-1990’s where he initially defined contracts as a set of promises agreed to in a “meeting of the minds” to “formalize a relationship”. Then later went to conceptualize how, by integrating digital technology, including cryptographic algorithms, with the idea of contracts, we would be able to create a digital promise which would still perform the four basic objectives of contract design including observability, verifiability, privity and enforceability.

    “A smart contract is a set of promises, specified in digital form, including protocols within which the parties perform on these promises.”

    Smart contracts are believed to improve efficiency with transactions/processes and also remove ambiguity as summarized below:

    Process efficiency

    As smart contracts feed from digital information, upon the conditions met in the smart contract, the agreed next step between parties will proceed automatically, i.e. processing of a bet between parties, or progressing application forms upon receipt of information.

    Remove ambiguity and third party involvement

    Current legal contracts are at times difficult to understand and may be interpreted differently between parties. Smart contracts (in the perspective of blockchains) are currently mainly written in code, and it is meant to be more black-and-white, hence ambiguity in legal contractual language is believed to be removed — this also removes the need for lawyers and/or governing officials to mediate the process.

    Further detail is readily available online (a discussion between members at the Wharton School of the University of Pennsylvania provides a good example).

    Smart Contracts in Blockchain

    Today, with the introduction of blockchain technology and various projects we have seen smart contracts realized in practice — a popular example is the Ethereum project. BOS Platform aims to further the smart contract functionality than currently on offer within today’s blockchain technologies.

    In designing smart contracts, various theories may be applied, and as presented in the next section, many have adopted a Turing-complete concept. Turing complete comes from computational automata theory where there are four major families of automaton: Finite-state machine; Pushdown automata; Linear-bounded automata; and Turing machine.

    BOS Platform adopts the Timed Automata, an extension of finite automata, for development of the Trust Contracts and also Web Ontology Language; as such, for the purposes of this article, we will focus our knowledge sharing on the Turing-machine and finite-state automata concepts for the development and functionality of smart contracts, as well as touching on some other more popular design options.

    CURRENT SMART CONTRACTS CONCEPTS

    Through reading various projects information on smart contracts at a design and architecture level, they appear to lack specificity and detail; this is probably because smart contracts are created to be adaptable to particular tasks and/or are project specific. Instead of trying to understand smart contracts at a general blockchain space, this article will look at specific blockchain projects’ design of smart contracts, where we will hopefully then gather a general feel of smart contracts in a public blockchain space.

    The list of cryptocurrencies below mainly relate to public blockchains’ smart contracts as this relates to BOScoin’s environment of operation.

    Public Blockchain Smart Contracts Notes

    Bitcoin

    Although the main goal of Bitcoin is the transaction of the Bitcoin currency in its platform, its openness allows smart contracts (with limited functionality) to be built onto the platform. One, for example is RootStock, a project which is built on Bitcoin’s blockchain. The consensus component of the RootStock is conducted via Bitcoin’s network, and adds a Turing complete smart contract on top of it.

    Ethereum

    Ethereum smart contracts are designed using a Turing complete concept whereby the smart contracts may run any program (irrespective of the language) provided it has the resource (gas or computational power). Due to this nature the only limit to the smart contract is if the contract is written in a way that causes issues and behaves inappropriately, or not as planned.

    A research by Bartoletti and Pompianu earlier this year studied the design aspects in relation to the operations of Ethereum smart contracts; and in summary they can be categorized into using blockchain, oracle or using a customized algorithm that may feed from blockchain or oracle information.

    Stellar

    Stellar only has simple smart contracts with “built-in token capabilities”. Stellar strives to ensure safety and stability of their system and has hence opted to limit their smart contract functionality.

    Lisk

    Using DPoS, Lisk smart contracts utilize a Turing complete concept with Node.js or JavaScript, however contracts are validated by programmers.

    Monax

    Monax supports the Ethereum’s smart contracts design, and further allow users to build private blockchains to define specific authorization policies to access the blockchains.

    Monax has defined smart contracts as code representing unilateral promises to provide deterministic computation based on transactions which are sent to the blockchain housed script.

    Monax looks to design smart contracts that are modular, repeatable, and have autonomous scripting which can be used to build applications; They wish their smart contracts to be mixed and matched, and easy to iterate, similar to lego bricks combined with pre-set templates, which can be coded to reflect any kind of data-driven business or engineering logic, or to model relationships and obligations.

    Nxt

    Nxt smart contracts are not Turing complete, but have used a Turing complete scripting layer to create template smart contracts. Users would select the most appropriate template and adjust the parameters to create their own smart contracts. Nxt believes the smart contracts created from these templates should cover most business applications; be easy to code, and ensure safety in the system.

    Tezos

    Tezos employs the Turing complete ideology, however they limit it by time and/or blocks on the blockchain.

    Tezos debates the theorems of Turing completeness that in practice and theory, computers are always bound by its computing resource (i.e. memory or electrical power), and hence will eventually halt.

    Qtum

    Using EVM Turing complete, Qtum aims to tailor this to Bitcoin’s UTXO model, whilst also adopting the Ethereum gas feature and creating their own smart contract language, Qtum Smart Contract Language (QSCL).

    Qtum will have an account abstraction layer, incorporated in their smart contract design, which translates the UTXO-based model to an account-based interface for the EVM.

    EOS

    EOS Focuses on asynchronous smart contracts which do not require sequential processing of current smart contracts (such as Ethereum), and hence are processed quicker. Unfortunately it appears EOS development in this front are being conducted under the covers until more is progressed.

    Waves

    Waves are adopting a non-turing complete concept using the Bitcoin scripting for their smart contracts to allow for finite execution times. There are also information on potentially having some transactions being processed off the chain to reduce blockchain bloat (unsure if this will be applied to smart contracts). Once again unfortunately, there is little information available to the public on other design aspects.

    Hyperledger

    Burrows is the permissionable Smart Contract Engine of Hyperledger. Components of Burrows include:

    • Consensus Engine - Currently using Tendermint’s consensus algorithm, however it aims to have the ability to leverage other consensus engines
    • Application Blockchain Interface (ABCI) - The interface — members are looking to make this component modular
    • Smart Contract Application Engine — validates transactions and applies them to the application state for consensus. Sub-components are: [Application Global State] The application state consists of all accounts, the validator set, and Burrow’s in-built name registry. [Secure native functions] Ground rules and coding policy for all smart contracts to adhere to [Permission Layer] [Permissioned EVM] Uses EVM combined with permission Finite amount of gas allocated for every execution to ensure finite duration [Gateway] Layer allowing clients to interact with the blockchain network and application state

    Other notes from research

    Not exactly another cryptocurrency, however upon research into smart contracts, there are various articles that provide some good information on smart contracts. Below summarizes some functionality limitations and other design considerations for smart contracts:

    • Regulating bugs in code
    • Tax on smart contract transactions (is this required? Potentially remove from article)
    • Sending wrong code
    • Terms in contracts do not cover the complete environment of the agreement, i.e. if external factors affect the practical operation of an agreement, the smart contract will continue to run (in legal contracts, you may rescind the contract)
    • All nodes will execute a smart contract

    On the last point regarding all nodes executing the same smart contract, some entities have incorporated an additional component into their architecture, Cryptlets. The concept of Cryptlets are an off-chain component that execute within a secure trusted container and communicated using secure channels.

    Public Blockchain Smart Contracts Design Aspects Summary

    From the information gathered above, there appears to be 3 categories of findings, Computational Automata design/modelling; Information sourcing and smart contract implementation.

    Computational Automata Design / Modeling

    A majority of projects have incorporated a Turing complete design into their smart contracts. Turing complete in a smart contract sense essentially allows to compute any program regardless of the language it is written in, with the thought of opening the potential of smart contracts functionality to be applicable to any environment.

    The concept of Turing completeness stems from the study of computational theory which the computational ability resembles that of a Turing Machine.

    Some other projects (i.e. Stellar and Bitcoin to an extent) have taken a different approach and not designed their smart contracts to be Turing complete or have created Turing complete smart contracts with limited functionality to uphold the safety and security of their platform.

    An example of where security and safety issues arose from Turing complete smart contracts is the DAO attack — where a hack was made to the DAO code to siphon funds, the security of the smart contract was made vulnerable to attacks as the implementation of the code was not completely understood.

    Information Sourcing

    In order for the implementation of a smart contract, there needs to be some form of input data which the contract processes and, upon certain agreed conditions met, it produces some resulting output. From the information gathered above, the input data appears to be of 2 forms, information from the blockchain itself, and information from some oracle source.

    Information from the blockchain appears to be the most reliable as the blockchain platform has been designed to ensure the integrity and safety of the information, agreed among the community network.

    Data from an oracle source, in contrast, may pose some quality and reliability concerns. How are we to know whether information from oracles are correct? Where is the information sourced from? Who has the permission to update the information? The list goes on.. Of course there may be sites where information is backed by reputable agencies, however who is to know for certain the information is credible?

    Implementation

    At a high level, blockchain is a decentralized system and all nodes essentially run the platform. Some sources have identified potential inefficiency regarding the operations of smart contracts stored on the blockchain requiring all nodes to implement it — if all nodes are implementing the same code, can we say this is an efficient use of resource?

    Websites used to understand good current smart contracts:



  • BOScoin Update - TokenNet Launch Postponed &Test Results & Wallet Testing




    TokenNet Launch Postponed

    TokenNet launch is not far off now, but unfortunately, delays must be
    made to ensure everything goes right upon launch due to Chuseok. Chuseok
    is one of the biggest holidays in Korea and is just after the intended
    deployment date of TokenNet. We originally did not anticipate Chuseok to
    be this long because the government designated Oct. 2nd
    to be a one off holiday only three weeks ago but we are having a long
    Chuseok this year, 10 days to be exact if you include the weekends from Sept. 30th to Oct. 9th.
    So, we have decided to let the team go home for once and spend the
    holidays with their families. Since not everyone on the team will be on
    stand by mode during that time, we feel it is safer to postpone TokenNet
    launch, especially being the first release of the platform/token.
    Nonetheless, most of our crew will continue further tests to launch
    TokenNet as best as we can. We will let you know of the exact date as
    soon as we are confident that we are able to meet that date. Also,
    as soon as Web-wallet functionality and UX modifications are completed,
    TestNet will be open to the public for you to check it out. We expect to
    open TestNet by the 29th at the latest.

    Test Results & Wallet Testing

    The testing program planned to test the SCP on the AWS network, after when codes are optimized we would move onto the TokenNet environment. Testing in both environments was conducted with various quorum & node configurations in 4 different regions (Virginia, Seoul, Sydney and Frankfurt - 9 nodes in each region). SCP tests are now complete and we have moved on to a mock TokenNet (TokenNet will be the replication of this mock TokenNet on the actual network) testing which we will focus on network stability based on stress testing (summary of test results are below for your reference). 

    Our initial SCP tests experienced high error rates when heavy traffic was injected to the network but our engineers fixed the problem by optimizing horizon configurations in sequencing the transactions. As of now, we are experiencing a 0% error rate but Virginia seems to drop out due to debugging messages that deplete the storage space for its server. We are currently working to resolve this matter and current thoughts believe the issue is due to the physical distance that cause high latency which will lead to less priority for any transaction coming out of that region. It takes at least 5 hours to run a single test so hence a slower than preferred progress rate, but we are working around the clock to fix it, so please do bear with us. 

    High level summary of results:

    • Quorum Configuration
      • Tested with 4 regions, 9 nodes and 1 horizon with each region - Virginia, Seoul, Sydney, Frankfurt - but Virginia seems to disconnect from the network for reasons yet unclear.
      • Restoring protocol to synch Virginia back to the network did not function properly - needs to be checked.
      • Despite the disconnection, the rest of the network remains stable and fully functional.
      • Network stability seems to increase with more nodes in the network.
    • Transaction Error Rates
      • Initially we were experiencing an exponential increase in the amount of errors proportionate to the amount of concurrent levels but after interrogating the code and protocol with further tests, we were able to keep the number to 0% for tests below the concurrent value of 300.
      • Error rates slowly rise if the concurrency value is beyond 300 and rises at a faster pace beyond 800 but such heavy traffic seems unlikely for TokenNet network environment. Error rate = failed transactions including transactions unprocessed for 60 seconds / all transactions
    • Latency
      • With the high error rate, we experienced 2~10 TPS, but once fixing the problem, we are getting around 20~30 TPS. Efforts are being made to increase transaction speed.
    • Other
      • Various codes from the Stellar Consensus Protocol were optimized to align to our TokenNet design such as:
        • Horizon/Sequence number
        • Change of TokenNet configuration such as issuance, base reserve, transaction fee etc.
      • External API matching and compatibility test
    • Web-Wallet 
      • Web-wallet functionality tests and UI/UX modifications are ongoing. A test version Web-wallet will be made public along with TestNet release by the end of next week.
      • We have engaged with a couple of web security firms and asked them to look into our Web-wallet security. We are waiting for results and hopefully we will receive some feedback by next week.

     

    Mathematics Session

    The BOS team engaged Dr. Jonghwan Lee, a Ph.D of Applied Mathematics from KAIST, to conduct 4 x 2hr sessions to further our understanding on the Stellar Consensus Protocol commencing Aug 28th, 2017. The first two sessions was to confirm our understanding on the Stellar Consensus Protocol Whitepaper; and the last 2 sessions were for us to interrogate the logic validity and also discuss on various design considerations for the BOS Platform. The team found the sessions to be very useful to bounce ideas on the undersanding of the Stellar Consensus Protocol and how it will be integrated within the BOS Platform. We would have attached a couple of photos of the session but Dr. Lee is extremely shy so we will only give you some key take-aways by individuals in our team. 

    "I now have a much better understanding of the quorum concept in the SCP - it is not a static definition which I was confused with at first. Having the sessions has helped me reach this understanding." - Hankyeol Tschoe

    "Having the sessions has allowed me to better understand and translate the intricate logic behind the consensus mechanism, especially regarding v-blocking." - Aston S. Nam

    In the next newsletter, we will let you know of the sessions on Timed Automata theory that we are currently having.

     

    Design Update & Homepage Refreshment

    As mentioned in the previous newsletter, we are in the process up updating our homepage in preparation for TokenNet!

    The main changes will relate to a design overhaul with the new BOScoin concept and we would like to take a little time to address the Design Identity of BOScoin that will be embedded in our new homepage, and future BOScoin products.

    The conventional shape of a coin is a circle but we wanted to incorporate the blockchain aspect into BOScoin's visual identity. A block is a square seen from the front but we wanted to give it twist and take a look from a different point of view. The square that is the block becomes a hexagon seen from an elevated angle, hence the hexagonal shape.

    The hexagon also resembles a single honeycomb by itself but put together, a beehive which symbolizes a decentralized ecosystem.

    The B inside represents BOScoin, and is also designed to resemble a chain.

    Dots on the front of our renewed homepage will start from a hexagon but will continually transform its shape to illustrate the evolving network/ecosystem. Please, don't be shy and tell us what you think.

    Below are some initial design work we are considering for our refreshed homepage:

       

    Have You Met...Hyonam Lee

    Background

    Hyonam is the chief designer for BlockchainOS and has been with the team since June. He has created and redefined the entire design language of BOScoin since joining the team, which includes the new homepage as well as the Web-wallet that will be launched soon. Hyonam originally studied fashion design and has spent some time in the fashion industry after finishing his studies. He later joined forces with a few freinds, set up a venture business where he was in charge of overall design for the firm - that is where his interest in web design sparked. Although Hyonam initially did not consider web design as a career, after so many unsatisfactory attempts in creating the firm's homepage by subcontractors, he decided to learn coding himself and that has stuck ever since. Following the venture business, he pursued a career in web design with anagency where he became the art director and project manager for big projects by companies like KT and Samsung. With the agency, Hyonam won several prestigious awards for his practical yet artistic work. Working in the IT industry, Hyonam's interests in blockchain grew and he wanted to be involved in a deeper, challenging and consistent project. The BOScoin team, being the first and only to have successfully managed a fundraiser so far in Korea, seemed like a good destination. BOScoin's prospects as a leading cryptocurrency led Hyonam to decide in joining the team as he can reach as many people around the globe through his work. 

     

    Hyonam's take on Blockchain

    Hyonam considers blockchain technology a tool of making the world more transparent and secure. Despite the current price volatility of cryptocurrencies, blockchain technology is here to stay in the long run and he is particularly excited with the BOScoin project. Hyonam wishes his work to be a positive influence on the development and value of BOScoin.

     

    Random Interesting Fact

    Hyonam's eventual goal, at a much later stage in life, is to become an architect. He wishes to build homes and design the interiors from scratch that convey his designing philosophy. A Passive House - an environmentally friendly house where energy consumption is minimized - is what he dreams to build.  

    Keep Up To Date!

    For daily conversations on the BOS Platform, including discussions or conversation with the wider community, please ensure you are also subscribed to our Slack.




  • BOScoin [BOS] Development Update - Test Web-Wallet & TokenNet Development Tests





    Development Update Happy Chuseok to everyone from the BOScoin team! We realize most of our contributors and subscribers do not have anything to do with Chuseok, which is a national holiday quite similar to what is thanksgiving in the US, but we thought our holiday sentiment could extend to you anyways:) The team has been working on tests and problems we mentioned before throughout the holidays nonetheless, and we do have some good news. Replacing Virginia to California proved to be fruitful and we are experiencing no disconnections. Error rates, which is defined as the failed transactions including transactions unprocessed for 60 seconds divided by all transactions, were also kept below 0.06% with an increased concurrency value of 400. This is great improvement compared to two weeks ago when a concurrency value beyond 300 returned a rapid rise in the error rate. Although these tests may seem unimportant, it allow us to better understand the network and enable us to deal with the situation more systematically, if any problems were to occur. It provides us with an idea of how the network behaves if anything goes as unexpected and where to look at to fix the problem once the network goes live.  We have also been working to increase the performance of the network. We have proven that more validating nodes increase the stability of the network by comparing a 9 node network to a 36 node network on our TestNet. Although this does not necessarily increase speed, a more stable network can be achieved. TPS fluctuation seems to lessen with more nodes and since we are testing on a harsh environment, we expect speed to improve when TokenNet is launched. Below is a short summary of what we have covered and screenshots of the results :

    TokenNet Development Tests


    • Replace Virginia to California - Increased network stability with no disconnections 
    • Decreased error rate with a concurrency value up to 400 (below 0.06% at 400)  






     

    Test Web-Wallet We would like to extend our thanks to everyone who have and are participating in testing our test Web-wallet. We have received many feedback and are currently working to reflect your comments. Modifications are constantly being made so we would still appreciate if you could provide input in improving the test Web-wallet. The test Web-wallet still needs to move to the TestNet and we will let you know when we do, but at the moment, please let us know if you see anything unfit regarding functionality, user-friendliness, design or any other aspect you wish to see improved.


  • BOScoin [BOS] IMPORTANT ANNOUNCEMENT

    BOS Platform Foundation Announcement

    On Friday, November 10, 2017, there was a temporary failure of the BOScoin network causing the blockchain consensus to fail. The team has been working on recovery during the weekend and has recovered the wallet balances for all accounts, the network was successfully restarted on November 12, 2017 at 15:00 (GMT), and is now running normally. However, only the wallet balances were recovered without the transaction history. The transaction history is kept separately and we are in the process of reviewing the recovery plan. More detailed information will be shared after inspection.

    November 13, 2017 BOS Platform Foundation

    Note: We will not be publishing details at this time. A full update will be provided to the community once the developers are complete.

    DO NOT SHARE YOUR SECRET SEED WITH ANYONE!!

    Everyone waiting more than two days for their coin distribution, check your wallet for coins, and if you have not received your distribution, make sure you sent the public address starting with “G” to [email protected], and also sent your public address and a valid email address to @BOS_tokennet on telegram or WeChat ID BOS_tokennet. (Note: There are fake BOS accounts on telegram, ensure you sent to telegram username: @BOS_tokennet) Follow the claim instructions at https://medium.com/@boscoin/newsletter-october-30th-2017-9dafb1801e5f. If you don’t send your information via telegram or WeChat you will not get your coins. Double check you sent the correct information to the correct accounts. Many people sent their information to the wrong account.

    Once you’ve determined you haven’t already received your coins, and you sent the correct information to the correct email and telegram/WeChat accounts, then send an email to [email protected].

    https://support.google.com/mail/contact/abuse ← — if you receive any email from [email protected], or any other email address pretending to be us, please let us know, and you can report them directly to google at the enclosed link. Thanks.

    Please report @bos_tokenet to telegram at [email protected] and [email protected] this account is attempting to phish you out of your secret seed, so please send telegram support emails requesting they ban this user from their platform.

    Distribution Status

    Statistics

    2555 users received their tokens out of 8538 total participants. We’ve distributed 244,633,981.71 BOS as of today, which is 59.3% of the total distribution.

    Distribution Schedule

    We will continue to accept token distribution requests, but we will process the transfers twice a week, on Monday and Friday.

    Follow this guide to claim your tokens. https://boscoin.io/docs/wallet-claim-guide-eng.pdf

    BOScoin Forum Update

    The forum can be found at https://forum.boscoin.io.

    The system email for both the dashboard and the forum is fixed. Looks like everyone who was pending activation on the forum was able to get into the forum and post. If anyone still has a problem with the forum or the dashboard, please email [email protected], and we will help you get access.

    Singapore Fintech Festival 13–17 Nov

    http://www.fintechfestival.sg/about/

    Hankyeol Tschoe (bos_hankyeol on slack) is attending the Singapore Fintech Festival with one of our community members (wouterb on slack). They are meeting with a few companies to discuss potential partnerships. They are attending the conference all week, so if you are attending the conference, or just in Singapore and would like to meet one of our team, then hit Hankyeol up on the slack.



  • BOScoin [BOS]  IMPORTANT ANNOUNCEMENT - Distribution Status, Distribution Schedule, Community Management Updates & More

    On Friday, November 10, 2017, there was a temporary failure of the BOScoin network causing the blockchain consensus logic to fail. This was announced (https://medium.com/@boscoin/bos-platform-foundation-announcement-fdd66d479f7c) and we recovered the blockchain to the last prior stable state, which included all balances, but did not include any transaction history. On Friday, November 17, 2017, we issued this announcement (https://medium.com/@boscoin/bos-platform-foundation-announcement-fef1cab6aa30) notifying the community there was an issue with the manual transfer of transaction fees to public addresses via a script which began processing at 12:25 GMT, 17 Nov 2017 and was halted at 15:04 GMT. This error was caused by a misplaced decimal in the code, which resulted in the distribution of 34 Million BOS to 1418 public addresses. The CTO and other senior management have evaluated the situation, and have decided on the following course of action.

    All public addresses will be reset to a token balance that includes all transfers conducted prior to the online wallet going off line at 15:04 GMT, but will NOT include the transaction fees transferred by the script in error. There will NOT be transaction history after the blockchain is reset. This solution will negate the faulty transaction fees transferred by the script, while at the same time keeping any transfers between public addresses prior to the online wallet being put into maintenance mode. The online wallet (https://wallet.boscoin.io) will be back online by 15:00 GMT 21 Nov 2017.

    We sincerely apologize for the complications caused for two consecutive weeks. The first error was due to a problem with the code and the second one was clearly a human error. Our development team will improve the code reviewing process as well as testings prior to the actual implementation of the code. We promise such mistakes will not be made again in the future.

    DO NOT SHARE YOUR SECRET SEED WITH ANYONE!!

    Before you email [email protected] asking if you’ve received your coins, please check your public address balance at one of the below websites after 15:00 GMT, 21 November 2017. These websites were created by community members.

    https://boscoin-a5759.firebaseapp.com/ created by dahammer https://bosradar.com/address/ created by bosradar http://boschain.org/pages/balance.php created by boschain

    Distribution Status

    Statistics

    2928 users received their tokens out of 8538 total participants. We’ve distributed 257,193,162.80 BOS as of today, which leaves 37.65% remaining to distribute.

    Distribution Schedule

    We will continue to accept token distribution requests, and process the transfers twice a week.  Follow this guide to claim your tokens. https://boscoin.io/docs/wallet-claim-guide-eng.pdf

    Community Management Updates

    The forum can be found at https://forum.boscoin.io.

    The system email for both the dashboard and the forum is currently down. This is being reviewed by our developers, and corrected.

    Singapore Trip 13–17 Nov

    Pictured — Wouter and Hankyeol

    Last week we participated in the Singapore Fintech Festival and checked out the international atmosphere surrounding Fintech, especially in the Blockchain scene. We had a few prearranged meetings with potential partners and the Fintech Festival wasn’t the main reason why we went to Singapore but it was nice to go out of South Korea and see how fast the industry is moving forward. We also participated in the Inclusive Blockchain Conference hosted by Singapore University of Social Sciences where Vitalik Buterin also had a brief session. Other prominent figures such as Toby Hoenisch from TenX, Los Luu from Kyber, Bobby Ong from Coingecko, Joseph Lubin from ConsenSys and Patrick Dai from Qtum also participated as panelists. Although we did not have a speaking session, it was good to see and learn the challenges others are facing as well. The main reason to go all the way out to Singapore was to see our potential partners and the business they are conducting and we are pleased with some of the progresses we have made. The most progress came from payment and security companies but as some of you may realize by now, we only publicize what is certain so we will update the community in the near future regarding any potential partnerships that may come from this conference.

    Applications Development Update

    The following are git commits published to the public github repositories which can be found at https://github.com/owlchain.

    TokenNet Wallet Development

    Nov 14, 2017 “Add install script” https://github.com/owlchain/tokennet-wallet/commit/bf7e7c96a7443bed4eea03ade0be540afaa8c9e2

    TokenNet Protocol Development

    Nov 16, 2017 “fixed; 5a6202a” https://github.com/owlchain/stellar-sdk-go/commit/37985fd8a6eab6fae0e70dce7d811186b0bbd66a

    “Merge branch ‘change-tx-fee’ into tokennet” https://github.com/owlchain/stellar-sdk-go/commit/f77fa9313308a5a76f74ca168a824d6269fe9a64

    “set the eBaseFee to uint64 type” https://github.com/owlchain/stellar-sdk-go/commit/5a6202a44daf1e9bd33379581d56abbfccfa0f02

    “Merge remote-tracking branch ‘official/master’” https://github.com/owlchain/stellar-sdk-go/commit/1314df88f9317f3a470420a056fecc82ee9f865a

    “reset the .gitignore” https://github.com/owlchain/stellar-sdk-go/commit/29a9470622e8c3cb909d699ce133ae0924f2e59d

    “fixed; to set the fee” https://github.com/owlchain/stellar-sdk-go/commit/755d074f9a407158ddf67114361a4daed6e569bc

    “fixed; to set the fee” https://github.com/owlchain/stellar-sdk-go/commit/5bfa0e2c0c92a0aae73e69f448913ec01749b4fa Nov 14, 2017 “prevent inflation and only one account can be possible” https://github.com/owlchain/stellar-sdk-go/commit/0671430dc15a1f94d3601be8287ee8a6fe5bfe18

    BOSnet Protocol Development

    The mFBA protocol for BOSnet (M3 Genesis) is under development in a private repository. The BOSnet mFBA consensus protocol will not be a continuation of our current TokenNet consensus protocol, but instead is the realization of Yezune Choi’s vision for the BOSnet platform written from scratch by our development team. The BOSnet mFBA protocol is undergoing testing and development.

    Have You Met…Eunseong Kang

    Eunseong Kang

    Eunseong Kang is our new Chief Information Security Officer (CISO). He comes to us with many years of senior information security experience.

    Background

    Eunseong has been working in IT for 30 years. He’s worked on security consulting and education, and also as a technical advisor for product security at LG Electronics. Prior to that, he worked as a CISO for an Internet company and as the head of R&D at the largest security company in Korea.

    Interests

    His interests include protecting the performance and value of colleagues above all. For the time being, all his attention and effort is placed into helping his colleagues.

    Random interesting fact

    Family trips are the happiest thing these days.



Looks like your connection to Cryptocentral was lost, please wait while we try to reconnect.