Tokenika wiki, Tokenika review, Tokenika history, Tokenika founders, Tokenika motto Tokenika ownership, Tokenika email, Tokenika address, Tokenika phone, Tokenika headquarters Tokenika news, what is Tokenika, where is Tokenika Tokenika wikipedia
Tokenika revenue, Tokenika employees, Tokenika location, Tokenika facts

Tokenika is an EOS block producer ​ candidate. [1] Warsaw ​-based, Tokenik is considered the Eastern European blockchain expert, software house and think-tank specialising in blockchain and distributed ledger technologies. [2] ​ Consisting of a strong team of experts from the fields of IT, coding, artificial intelligence, trading, law and regulatory environments, they strive to create a foundation for the most promising blockchain related tech. [3] [4] [5]

Youtube Video
Tokenika @EOSgo, an EOS block producer candidate interview.

The location of their block producing servers will be located at three datacenters in Warsaw ​, Cracow ​ and Katowice ​. [6]


Public Presence [7] [8] [9] [10]

Logo of Tokenika as an EOS Block Producers that has been shared on their Steemit. [1]

ID on Steemit

  • Official block producer candidate name: Tokenika [11]
  • Location of company headquarters: Warsaw, Poland [12]
  • Expected location of servers: three datacenters located in Warsaw, Cracow and Katowice. [13]
  • Type of servers: mainly bare metal but also cloud for quick scaling [14]
  • Current employee list and pictures of at least 67% of staff: [15]
  • Relevant background qualifications for at least 67% of staff: [16]

Tech Specs

  • They are using tier 3+ datacenters across Poland in 3 different cities with plenty of room for growth (20-40 rack units in each). Available now, more if needed.
  • Tier datacenter standards. [17]
  • They will have 3 main servers: Nike , Wawel & Hanys (Dual Xeon E5-2687W with 512GB RAM ECC DDR4). Plus a bunch of other boxes powering our base infrastructure. [18]
  • That gives 24 cores (48 threads) per machine for a total of 72 cores or 144 threads, which powered by up to 3.5GHz gives excellent single-core performance. [19]
  • At least two of them will be available from day one to deal with our basic needs.
  • They served them well for months, and they are switching from SSDs to NVMes, as their base storage and adding some RAM. [20]
  • Total resource expenditures by June 3rd should come in around $20k. [21]

Scaling Plan

  • For Nikatoken, it's not the hardware specs that make them feel ready for EOS launch. It's the ability to scale rapidly. They are expecting the unexpected. [22]
  • They are partnered with external infrastructure providers ready to boost their processing power within minutes. Thus, in the event of very heavy loads, they are able to expand our datacenter capacity by orders of magnitude in near real-time. [23]
  • Additionally, they plan to use cloud solutions, including SDDC (software-defined datacenter). [24]
  • Initially, when nobody knows what the actual demand for processing power is going to be, they'll be to some degree dependent on our partners (i.e. external providers). [25]

Youtube Video
Tokenika @ EOS Oslo Meetup, 17th Janunary 2018.

Community Projects

As a software house and an EOS decicated incubator, they are currently involved in development of several projects for the EOS blockchain. [26] ​ These are:

  • EOSPROJECTS, a comprehensive listing of all tools and initiatives making up the EOS ecosystem.
  • EOSPROBE - not only a block explorer but also a tool for monitoring witnesses' performance, similar to Steem's SteemDB.
  • EOSFACTORY, a framework for compiling, testing and deploying EOS smart-contracts, similar to Ethereum's Truffle Framework.
  • SYGNET - an EOS-based digital identity system. [27]

They have a proven track record in supporting the EOS community since its beginnings that can be verified on their Github profile. [28] ​ They have spoken at conferences and meetups promoting EOS, been a heavy supporter of Dan Larimer ​'s projects since early days of Bitshares ​ (around 2013) and have regularly contributed to promotion of EOS since its inception. [29]

Their team members manage one of the best performing Steem witness nodes, consistently scoring in the top 3 for the least amount of dropped blocks. This separates them from other witness candidates with no track record or expertise, with a history of a only a few SM posts, dating several weeks back at best. They are also aware of the utilitarian role of a witness node, and in the event of a high surplus of income from the witness voting, we are planning to set up a transparent, blockchain auditable software incubator that redistributes a certain percentage of the witness income towards finding and promotion of most interesting startups. The precise formula of this will be worked out when the economics of an EOS witness node become more clear. [30]

Community Projects

Our recent release of EOSFactory is a good example of contribution to the EOS community - by popular demand we provided an important solution for testing and writing smart contracts, and open-sourced it. This is our modus operandi in general - we create things and share the results, within reasonable business constraints. [31]

They currently have two more big dApp projects (Sygnet, mentioned earlier, and another to be disclosed soon) in the pipeline, plus a very likely airdrop for one of them. That, however, have nothing to do with the BP mission, and are separate dApps with benefit for the whole community. As to precise timeline, we are aiming for a release of one of the mentioned projects in late 2018 or early 2019, depending on the smoothness of the development process. [32]

Telegram + Testnet

Telegram: tokenika [33]

Testnet: rogue [ 34]

Block Producer Roadmap

EOSFactory is still under development. Right now they are working on the following features [35] ​:

  • Upgrading to a more advanced mechanism for creating and managing unit-tests. They will be stored as a hierarchy of Python files, in a similar way the process is organized in Ethereum's Truffle Framework- they use Python instead of JavaScript. Also, they plan to add support for other IDEs, e.g. Eclipse. [36]
  • Secondly, they are considering the pros and cons of connecting with their Python layer directly to cleos , the official EOS CLI. When they started working on EOSFactory, cleos (at that time named eosc ) was in a bad shape and thus not suitable for our needs, so they had to build their own C++ interface to an EOS node. As things get smoother, they might reconsider relying on cleos . [37]
  • And finally, they are thinking about integrating Ricardian Contracts into our unit-testing. This is a very interesting (and probably not widely known at this stage) aspect of EOS smart-contracts. For more information please refer to EOSIO documentation. [38]

They plan to have the next release of EOSFactory in a couple of weeks, ideally before EOS is launched. [39]

Position on Dividends

They are against vote buying in any form or shape, and are not, and will not be offering any profit sharing with their voters. Their contribution to the system has always been in form of adding value, and not crude redistribution of income. They will abide by the EOS constitution at all times - Tokenika’s BP is a mere servant, and at best, an advisor for the EOS community, even if the public ruling stands in conflict with their personal views. [40]

They are not advocates for heavy regulation of business practices around EOS. In their view, young distributed systems must find a natural market equilibrium. Stark regulation, arbitration and other penalising measures open up a can of worms, in which authority has to be imposed externally, and might result in forking of chains, endless disputes, or even render the system unstable. [41]

The team of Tokenika are mostly libertarians at heart and believe that market forces always find a way to balance things out. [42]

All information for Tokenika's wiki comes from the below links. Any source is valid, including Twitter, Facebook, Instagram, and LinkedIn. Pictures, videos, biodata, and files relating to Tokenika are also acceptable encyclopedic sources.
Other wiki pages related to Tokenika.