Bitschablon, easy, fast, safe trading btc through bits ...

Function X: A Concept Paper introducing the f(x) ecosystem, a universal decentralized internet powered by blockchain technology and smart devices

Function X: A Concept Paper introducing the f(x) ecosystem, a universal decentralized internet powered by blockchain technology and smart devices

https://preview.redd.it/yylq6k0yqrv21.png?width=633&format=png&auto=webp&s=089ffe83e18baeceb87d465ca6fad184939490e4

Prologue

This is a Concept Paper written to introduce the Function X Ecosystem, which includes the XPhone. It also addresses the relationship between the XPOS and Function X.
Pundi X has always been a community-driven project. We have lived by the mission of making sure the community comes first and we are constantly learning from discussions and interactions on social media and in real-life meetings.
As with all discussions, there is always background noise but we have found gems in these community discussions. One such example is a question which we found constantly lingering at the back of our mind, “Has blockchain changed the world as the Internet did in the ’90s, and the automobile in the ‘20s?”. Many might argue that it has, given the rise of so many blockchain projects with vast potential in different dimensions (like ours, if we may add). But the question remains, “can blockchain ever become what the Internet, as we know it today, has to the world?”
Function X, a universal decentralized internet which is powered by blockchain technology and smart devices.
Over the past few months, in the process of implementing and deploying the XPOS solution, we believe we found the answer to the question. A nimble development team was set up to bring the answer to life. We discovered that it is indeed possible to bring blockchain to the world of telephony, data transmission, storage and other industries; a world far beyond financial transactions and transfers.
This is supported by end-user smart devices functioning as blockchain nodes. These devices include the XPOS and XPhone developed by Pundi X and will also include many other hardware devices manufactured by other original equipment manufacturers.
The vision we want to achieve for f(x) is to create a fully autonomous and decentralized network that does not rely on any individual, organization or structure.
Due to the nature of the many new concepts introduced within this Concept Paper, we have included a Q&A after each segment to facilitate your understanding. We will continuously update this paper to reflect the progress we’re making.

Function X: The Internet was just the beginning

The advent of the Internet has revolutionized the world. It created a communications layer so robust that it has resulted in TCP/IP becoming the network standard.
The Internet also created a wealth of information so disruptive that a company like Amazon threatened to wipe out all the traditional brick-and-mortar bookstores. These bookstores were forced to either adapt or perish. The same applies to the news publishing sector: the offerings of Google and Facebook have caused the near extinction of traditional newspapers.
The digitalization of the world with the Internet has enabled tech behemoths like Apple, Amazon, Google and Facebook to dominate and rule over traditional companies. The grip of these tech giants is so extensive that it makes you wonder if the choices you make are truly your own or influenced by the data they have on you as a user.
We see the blockchain revolution happening in three phases. The first was how Bitcoin showed the world what digital currency is. The second refers to how Ethereum has provided a platform to build decentralized assets easily. The clearest use case of that has come in the form of the thousands of altcoins seen today that we all are familiar with. The third phase is what many blockchain companies are trying to do now: 1) to bring the performance of blockchain to a whole new level (transaction speed, throughput, sharding, etc.) and 2) to change the course of traditional industries and platforms—including the Internet and user dynamics.
Public blockchains allow trustless transactions. If everything can be transacted on the blockchain in a decentralized manner, the information will flow more efficiently than traditional offerings, without the interception of intermediators. It will level the playing field and prevent data monopolization thus allowing small innovators to develop and flourish by leveraging the resources and data shared on the blockchain.

The Blockchain revolution will be the biggest digital revolution

In order to displace an incumbent technology with something new, we believe the change and improvement which the new technology has to bring will have to be at least a tenfold improvement on all aspects including speed, transparency, scalability and governance (consensus). We are excited to say that the time for this 10-times change is here. It’s time to take it up 10x with Function X.
Function X or f(x) is an ecosystem built entirely on and for the blockchain. Everything in f(x) (including the application source code, transmission protocol and hardware) is completely decentralized and secure. Every bit and byte in f(x) is part of the blockchain.
What we have developed is not just a public chain. It is a total decentralized solution. It consists of five core components: Function X Operating System (OS); Function X distributed ledger (Blockchain); Function X IPFS; FXTP Protocol and Function X Decentralized Docker. All five components serve a single purpose which is to decentralize all services, apps, websites, communications and, most importantly, data.
The purpose of Function X OS is to allow smart hardware and IoTs to harness the upside and potential utility of the decentralization approach. We have built an in-house solution for how mobile phones can leverage Function X OS in the form of the XPhone. Other companies can also employ the Function X OS and further customize it for their own smart devices. Every smart device in the Function X ecosystem can be a node and each will have its own address and private key, uniquely linked to their node names. The OS is based on the Android OS 9.0, therefore benefiting from backward compatibility with Android apps. The Function X OS supports Android apps and Google services (referred to as the traditional mode), as well as the newly developed decentralized services (referred to as the blockchain mode). Other XPhone features powered by the Function X OS will be elaborated on in the following sections.
Using the Function X Ecosystem (namely Function X FXTP), the transmission of data runs on a complex exchange of public and private key data and encryption but never through a centralized intermediary. Hence it guarantees communication without interception and gives users direct access to the data shared by others. Any information that is sent or transacted over the Function X Blockchain will also be recorded on the chain and fully protected by encryption so the ownesender has control over data sharing. And that is how a decentralized system for communications works.
For developers and users transitioning to the Function X platform, it will be a relatively seamless process. We have intentionally designed the process of creating and publishing new decentralized applications (DApps) on Function X to be easy, such that the knowledge and experience from developing and using Android will be transferable. With that in mind, a single line of code in most traditional apps can be modified, and developers can have their transmission protocol moved from the traditional HTTP mode (centralized) to a decentralized mode, thus making the transmission “ownerless” because data can transmit through the network of nodes without being blocked by third parties. How services can be ported easily or built from scratch as DApps will also be explained in the following sections, employing technologies in the Function X ecosystem (namely Function X IPFS, FXTP Protocol and Decentralized Docker).

f(x) Chain

f(x) chain is a set of consensus algorithms in the form of a distributed ledger, as part of the Function X ecosystem. The blockchain is the building block of our distributed ledger that stores and verifies transactions including financials, payments, communications (phone calls, file transfers, storage), services (DApps) and more.
Will Function X launch a mainnet?
Yes. The f(x) chain is a blockchain hence there will be a mainnet.
When will the testnet be launched?
Q2 2019 (projected).
When will the mainnet be launched?
Q3 2019 (projected).
How is the Function X blockchain designed?
The f(x) chain is designed based on the philosophy that any blockchain should be able to address real-life market demand of a constantly growing peer-to-peer network. It is a blockchain with high throughput achieved with a combination of decentralized hardware support (XPOS, XPhone, etc.) and open-source software toolkit enhancements.
What are the physical devices that will be connected to the Function X blockchain?
In due course, the XPOS OS will be replaced by the f(x) OS. On the other hand, the XPhone was designed with full f(x) OS integration in mind, from the ground up. After the f(x) OS onboarding, and with adequate stability testings and improvements, XPOS and XPhone will then be connected to the f(x) Chain.
What are the different elements of a block?
Anything that is transmittable over the distributed network can be stored in the block, including but not limited to phone call records, websites, data packets, source code, etc. It is worth noting that throughout these processes, all data is encrypted and only the owner of the private key has the right to decide how the data should be shared, stored, decrypted or even destroyed.
Which consensus mechanism is used?
Practical Byzantine Fault Tolerance (PBFT).
What are the other implementations of Practical Byzantine Fault Tolerance (PBFT)?
Flight systems that require very low latency. For example, SpaceX’s flight system, Dragon, uses PBFT design philosophy. [Appendix]
How do you create a much faster public chain?
We believe in achieving higher speed, thus hardware and software configurations matter. If your hardware is limited in numbers or processing power, this will limit the transaction speed which may pose security risks. The Ethereum network consists of about 25,000 nodes spread across the globe now, just two years after it was launched. Meanwhile, the Bitcoin network currently has around 7,000 nodes verifying the network. As for Pundi X, with the deployment plan (by us and our partners) for XPOS, XPhone and potentially other smart devices, we anticipate that we will be able to surpass the number of Bitcoin and Ethereum nodes within 1 to 2 years. There are also plans for a very competitive software implementation of our public blockchain, the details for which we will be sharing in the near future.

f(x) OS

The f(x) OS is an Android-modified operating system that is also blockchain-compatible. You can switch seamlessly between the blockchain and the traditional mode. In the blockchain mode, every bit and byte is fully decentralized including your calls, messages, browsers and apps. When in traditional mode, the f(x) OS supports all Android features.
Android is the most open and advanced operating system for smart hardware with over 2 billion monthly active users. Using Android also fits into our philosophy of being an OS/software designer and letting third-party hardware makers produce the hardware for the Function X Ecosystem.
What kind of open source will it be?
This has not been finalized, but the options we are currently considering are Apache or GNU GPLv3.
What kind of hardware will it work on?
The f(x) OS works on ARM architecture, hence it works on most smartphones, tablet computers, smart TVs, Android Auto and smartwatches in the market.
Will you build a new browser?
We are currently using a modified version of the Google Chrome browser. The browser supports both HTTP and FXTP, which means that apart from distributed FXTP contents, users can view traditional contents, such ashttps://www.google.com.
What is the Node Name System (NNS)?
A NNS is a distributed version of the traditional Domain Name System. A NNS allows every piece of Function X hardware, including the XPhone, to have a unique identity. This identity will be the unique identifier and can be called anything with digits and numbers, such as ‘JohnDoe2018’ or ‘AliceBob’. More on NNS in the following sections.
Will a third-party device running the f(x) OS be automatically connected to the f(x) blockchain?
Yes, third-party devices will be connected to the f(x) blockchain automatically.

f(x) FXTP

A transmission protocol defines the rules to allow information to be sent via a network. On the Internet, HTTP is a transmission protocol that governs how information such as website contents can be sent, received and displayed. FXTP is a transmission protocol for the decentralized network.
FXTP is different from HTTP because it is an end-to-end transmission whereby your data can be sent, received and displayed based on a consensus mechanism rather than a client-server based decision-making mechanism. In HTTP, the server (which is controlled by an entity) decides how and if the data is sent (or even monitored), whereas in FXTP, the data is sent out and propagates to the destination based on consensus.
HTTP functions as a request–response protocol in the client-server computing model. A web browser, for example, may be the client and an application running on a computer hosting a website may be the server. FXTP functions as a propagation protocol via a consensus model. A node that propagates the protocol and its packet content is both a “client” and a “server”, hence whether a packet reaches a destination is not determined by any intermediate party and this makes it more secure.

f(x) IPFS

IPFS is a protocol and network designed to store data in a distributed system. A person who wants to retrieve a file will call an identifier (hash) of the file, IPFS then combs through the other nodes and supplies the person with the file.
The file is stored on the IPFS network. If you run your own node, your file would be stored only on your node and available for the world to download. If someone else downloads it and seeds it, then the file will be stored on both your node the node of the individual who downloaded it (similar to BitTorrent).
IPFS is decentralized and more secure, which allows faster file and data transfer.

f(x) DDocker

Docker is computer program designed to make it easier to create, deploy, and run applications. Containers allow a developer to package up an application including libraries, and ship it all out as a package.
As the name suggests, Decentralized Docker is an open platform for developers to build, ship and run distributed applications. Developers will be able to store, deploy and run their codes remote in different locations and the codes are secure in a decentralized way.

XPhone

Beyond crypto: First true blockchain phone that is secured and decentralized to the core
XPhone is the world’s first blockchain phone which is designed with innovative features that are not found on other smartphones.
Powered by Function X, an ecosystem built entirely on and for the blockchain, XPhone runs on a new transmission protocol for the blockchain age. The innovation significantly expands the use of blockchain technology beyond financial transfers.
Unlike traditional phones which require a centralized service provider, XPhone runs independently without the need for that. Users can route phone calls and messages via blockchain nodes without the need for phone numbers.
Once the XPhone is registered on the network, for e.g., by a user named Pitt, if someone wants to access Pitt’s publicly shared data or content, that user can just enter FXTP://xxx.Pitt. This is similar to what we do for the traditional https:// protocol.
Whether Pitt is sharing photos, data, files or a website, they can be accessed through this path. And if Pitt’s friends would like to contact him, they can call, text or email his XPhone simply by entering “call.pitt”, “message.pitt”, or “mail.pitt”.
The transmission of data runs on a complex exchange of public and private key data with encryption. It can guarantee communication without interception and gives users direct access to the data shared by others. Any information that is sent or transacted over the Function X Blockchain will also be recorded on the chain.
Toggle between now and the future
Blockchain-based calling and messaging can be toggled on and off on the phone operating system which is built on Android 9.0. XPhone users can enjoy all the blockchain has to offer, as well as the traditional functionalities of an Android smartphone.
We’ll be sharing more about the availability of the XPhone and further applications of Function X in the near future.

DApps

DApps for mass adoption
So far the use of decentralized applications has been disappointing. But what if there was a straightforward way to bring popular, existing apps into a decentralized environment, without rebuilding everything? Until now, much of what we call peer-to-peer or ‘decentralized’ services continue to be built on centralized networks. We set out to change that with Function X; to disperse content now stored in the hands of the few, and to evolve services currently controlled by central parties.
Use Cases: Sharing economy
As seen from our ride-hailing DApp example that was demonstrated in New York back in November 2018, moving towards true decentralization empowers the providers of services and not the intermediaries. In the same way, the XPhone returns power to users over how their data is being shared and with whom. Function X will empower content creators to determine how their work is being displayed and used.
Use Cases: Free naming
One of the earliest alternative cryptocurrencies, Namecoin, wanted to use a blockchain to provide a name registration system, where users can register their names to create a unique identity. It is similar to the DNS system mapping to IP addresses. With the Node Name System (NNS) it is now possible to do this on the blockchain.
NNS is a distributed version of the traditional Domain Name System. A NNS allows every piece of Function X hardware, including the XPhone, to have a unique identifier that can be named anything with digits and numbers, such as ‘JohnDoe2018’ or ‘AliceBob’.
Use Cases: Mobile data currency
According to a study, mobile operator data revenues are estimated at over $600 billion USD by 2020, equivalent to $50 billion USD per month [appendix]. Assuming users are able to use services such as blockchain calls provided by XPhone (or other phones using Function X) the savings will be immense and the gain from profit can be passed on to providers such as DApp developers in Function X. In other words, instead of paying hefty bills to a mobile carrier for voice calls, users can pay less by making blockchain calls, and the fees paid are in f(x) coins. More importantly users will have complete privacy over their calls.
Use Cases: Decentralized file storage
Ethereum contracts claim to allow for the development of a decentralized file storage ecosystem, “where individual users can earn small quantities of money by renting out their own hard drives and unused space can be used to further drive down the costs of file storage.” However, they do not necessarily have the hardware to back this up. With the deployment of XPOS, smart hardware nodes and more, Function X is a natural fit for Decentralized File Storage. In fact, it is basically what f(x) IPFS is built for.
These are just four examples of the many use cases purported, and there can, will and should be more practical applications beyond these; we are right in the middle of uncharted territories.

Tokenomics

Decentralized and autonomous
The f(x) ecosystem is fully decentralized. It’s designed and built to run autonomously in perpetuity without the reliance or supervision of any individual or organization. To support this autonomous structure, f(x) Coin which is the underlying ‘currency’ within the f(x) ecosystem has to be decentralized in terms of its distribution, allocation, control, circulation and the way it’s being generated.
To get the structure of f(x) properly set up, the founding team will initially act as ‘initiators’ and ‘guardians’ of the ecosystem. The role of the team will be similar to being a gatekeeper to prevent any bad actors or stakeholders playing foul. At the same time, the team will facilitate good players to grow within the ecosystem. Once the f(x) ecosystem is up and running, the role of the founding team will be irrelevant and phased out. The long term intention of the team is to step away, allowing the ecosystem to run and flourish by itself.

Utility

In this section, we will explore the utility of the f(x) Coin. f(x) Coin is the native ‘currency’ of the Function X blockchain and ecosystem. All services rendered in the ecosystem will be processed, transacted with, or “fueled” by the f(x) Coin. Some of the proposed use cases include:
  • For service providers: Getting paid by developers, companies and consumers for providing storage nodes, DDocker and improvement of network connections. The role of service providers will be described in greater detail in the rest of the paper.
  • For consumers: Paying for service fees for the DApps, nodes, network resources, storage solutions and other services consumed within the f(x) ecosystem.
  • For developers: Paying for services and resources rendered in the ecosystem such as smart contract creation, file storage (paid to IPFS service provider), code hosting (paid to DDocker service provider), advertisements (paid to other developers) and design works. Developers can also get paid by enterprises or organizations that engaged in the developer’s services.
  • For enterprises or organizations: Paying for services provided by developers and advertisers. Services provided to consumers will be charged and denominated in f(x) Coin.
  • For phone and hardware manufacturers: Paying for further Function X OS customizations. It is worth noting that Pundi X Labs plan to only build a few thousand devices of the XPhone flagship handsets, and leave the subsequent market supply to be filled by third-party manufacturers using our operating system.
  • For financial institutions: receiving payments for financial services rendered in the ecosystem.
  • Applications requiring high throughput.
Hence f(x) Coin can be used as ‘currency’ for the below services,
  • In-app purchases
  • Blockchain calls
  • Smart contract creations
  • Transaction fees
  • Advertisements
  • Hosting fees
  • Borderless/cross-border transactions
We believe f(x) Coin utilization will be invariably higher than other coins in traditional chains due to the breadth of the f(x) ecosystem. This includes storage services and network resources on f(x) that will utilize the f(x) Coin as “fuel” for execution and validation of transactions.
Example 1: A developer creates a ride-hailing DApp called DUber.
DUber developer first uploads the image and data to IPFS (storage) and code to DDocker, respectively. The developer then pays for a decentralized code hosting service provided by the DDocker, and a decentralized file hosting service provided by the IPFS. Please note the storage hosting and code hosting services can be provided by a company, or by a savvy home user with smart nodes connected to the Function X ecosystem. Subsequently, a DUber user pays the developer.
Example 2: User Alice sends an imaginary token called ABCToken to Bob.
ABCToken is created using Function X smart contract. Smart nodes hosted at the home of Charlie help confirms the transaction, Charlie is paid by Alice (or both Alice and Bob).

The flow of f(x) Coin

Four main participants in f(x): Consumer (blue), Developer (blue), Infrastructure (blue), and Financial Service Provider (green)
Broadly speaking, there can be four main participants in the f(x) ecosystem, exhibited by the diagram above:
  • Consumer: Users enjoy the decentralized services available in the f(x) ecosystem
  • Infrastructure Service Provider: Providing infrastructures that make up the f(x) ecosystem such as those provided by mobile carriers, decentralized clouds services.
  • Developer: Building DApp on the f(x) network such as decentralized IT, hospitality and financial services apps.
  • Financial Service Provider: Providing liquidity for the f(x) Coin acting as an exchange.
The f(x) ecosystem’s value proposition:
  • Infrastructure service providers can offer similar services that they already are providing in other markets such as FXTP, DDocker and IPFS, to earn f(x) Coin.
  • Developers can modify their existing Android apps to be compatible with the f(x) OS environment effortlessly, and potentially earn f(x) Coin.
  • Developers, at the same time, also pay for the infrastructure services used for app creation.
  • Consumers immerse in the decentralized app environments and pay for services used in f(x) Coin.
  • Developer and infrastructure service providers can earn rewards in f(x) Coin by providing their services. They can also monetize it through a wide network of financial service providers to earn some profit, should they decide to do so.
Together, the four participants in this ecosystem will create a positive value flow. As the number of service providers grow, the quality of service will be enhanced, subsequently leading to more adoption. Similarly, more consumers means more value is added to the ecosystem by attracting more service providers,and creating f(x) Coin liquidity. Deep liquidity of f(x) Coin will attract more financial service providers to enhance the stability and quality of liquidity. This will attract more service providers to the ecosystem.
Figure: four main participants of the ecosystem The rationale behind f(x) Coin generation is the Proof of Service concept (PoS)
Service providers are crucial in the whole f(x) Ecosystem, the problem of motivation/facilitation has become our priority. We have to align our interests with theirs. Hence, we have set up a Tipping Jar (similar to mining) to motivate and facilitate the existing miners shift to the f(x) Ecosystem and become part of the infrastructure service provider or attract new players into our ecosystem. Income for service provider = Service fee (from payer) + Tipping (from f(x) network generation)
The idea is that the f(x) blockchain will generate a certain amount of f(x) Coin (diminishing annually) per second to different segments of service provider, such as in the 1st year, the f(x) blockchain will generate 3.5 f(x) Coin per second and it will be distributed among the infrastructure service provider through the Proof of Service concept. Every service provider such as infrastructure service providers, developers and financial service providers will receive a ‘certificate’ of Proof of Service in the blockchain after providing the service and redeeming the f(x) Coin.
Example: There are 3 IPFS providers in the market, and the total Tipping Jar for that specific period is 1 million f(x) Coin. Party A contributes 1 TB; Party B contributes 3 TB and Party C contributes 6 TB. So, Party A will earn 1/10 * 1 million = 100k f(x) Coin; Party B will earn 3/10 * 1 million = 300k f(x) Coin. Party C will earn 6/10 * 1 million = 600k f(x) Coin.
Note: The computation method of the distribution of the Tipping Jar might vary due to the differences in the nature of the service, period and party.
Figure: Circulation flow of f(x) Coin
The theory behind the computation.
Blockchain has integrated almost everything, such as storage, scripts, nodes and communication. This requires a large amount of bandwidth and computation resources which affects the transaction speed and concurrency metric.
In order to do achieve the goal of being scalable with high transaction speed, the f(x) blockchain has shifted out all the ‘bulky’ and ‘heavy duty’ functions onto other service providers, such as IPFS, FXTP, etc. We leave alone what blockchain technology does best: Calibration. Thus, the role of the Tipping Jar is to distribute the appropriate tokens to all participants.
Projected f(x) Coin distribution per second in the first year
According to Moore’s Law, the number of transistors in a densely integrated circuit doubles about every 18 -24 months. Thus, the performance of hardware doubles every 18-24 months. Taking into consideration Moore’s Law, Eric Schmidt said if you maintain the same hardware specs, the earnings will be cut in half after 18-24 months. Therefore, the normal Tipping Jar (reward) for an infrastructure service provider will decrease 50% every 18 months. In order to encourage infrastructure service providers to upgrade their hardware, we have set up another iteration and innovation contribution pool (which is worth of 50% of the normal Tipping Jar on the corresponding phase) to encourage the infrastructure service provider to embrace new technology.
According to the Andy-Bill’s law, “What Andy gives, Bill takes away”; software will always nibble away the extra performance of the hardware. The more performance a piece of hardware delivers, the more the software consumes. Thus, the developer will always follow the trend to maintain and provide high-quality service. The Tipping Jar will increase by 50% (based upon the previous quota) every 18 months.
Financial service providers will have to support the liquidation of the whole ecosystem along the journey, the Tipping Jar (FaaS) will increase by 50% by recognizing the contribution and encouraging innovation.
From the 13th year (9th phase), the Tipping Jar will reduce by 50% every 18 months. We are well aware that the “cliff drop” after the 12th year is significant. Hence, we have created a 3year (two-phase) diminishing transition period. The duration of each phase is 18 months. There are 10 phases in total which will last for a total of 15 years.
According to Gartner’s report, the blockchain industry is forecast to reach a market cap of
3.1 trillion USD in 2030. Hence, we believe a Tipping Jar of 15 years will allow the growth of Function X into the “mature life cycle” of the blockchain industry.

f(x) Coin / Token Allocation

Token allocation We believe great blockchain projects attempt to equitably balance the interests of different segments of the community. We hope to motivate and incentivize token holders by allocating a total of 65% of tokens from the Token Generation Event (TGE). Another 20% is allocated to the Ecosystem Genesis Fund for developer partnerships, exchanges and other such related purposes. The remaining 15% will go to engineering, product development and marketing. There will be no public or private sales for f(x) tokens.
NPXS / NPXSXEM is used to make crypto payments as easy as buying bottled water, while f(x) is used for the operation of a decentralized ecosystem and blockchain, consisting of DApps and other services. NPXS / NPXSXEM will continue to have the same functionality and purpose after the migration to the Function X blockchain in the future. Therefore, each token will be expected to assume different fundamental roles and grant different rights to the holders.
https://preview.redd.it/xohy6c6pprv21.png?width=509&format=png&auto=webp&s=a2c0bd0034805c5f055c3fea4bd3ba48eb59ff07
65% of allocation for NPXS / NPXSXEM holders is broken down into the following: 15% is used for staking (see below) 45% is used for conversion to f(x) tokens. (see below) 5% is used for extra bonus tasks over 12 months (allocation TBD).

https://preview.redd.it/6jmpfhmxprv21.png?width=481&format=png&auto=webp&s=c9eb2c124e0181c0851b7495028a317b5c9cd6b7
https://preview.redd.it/1pjcycv0qrv21.png?width=478&format=png&auto=webp&s=c529d5d99d760281efd0c3229edac494d5ed7750
Remarks All NPXS / NPXSXEM tokens that are converted will be removed from the total supply of NPXS / NPXSXEM; Pundi X will not convert company's NPXS for f(x) Tokens. This allocation is designed for NPXS/NPXSXEM long term holders. NPXS / NPXSXEM tokens that are converted will also be entitled to the 15% f(x) Token distribution right after the conversion.

Usage

Management of the Ecosystem Genesis Fund (EGF)
The purpose of setting up the Ecosystem Initialization Fund, is to motivate, encourage and facilitate service providers to join and root into the f(x) Ecosystem and, at the same time, to attract seed consumers to enrich and enlarge the f(x) Ecosystem. EIF comes from funds raised and will be used as a bootstrap mechanism to encourage adoption before the Tipping Jar incentives fully kicks in.
The EGF is divided into 5 parts:
  1. Consumer (10%): To attract consumers and enlarge the customer base;
  2. Developer (20%): To encourage developers to create DApps on the f(x) blockchain;
  3. Infrastructure Service Provider (20%): To set up or shift to the f(x) infrastructure;
  4. Financial Service Provider (20%): To create a trading platform for f(x) Coin and increase liquidity; and
  5. Emergency bridge reserve (30%): To facilitate or help the stakeholders in f(x) during extreme market condition
To implement the spirit of decentralization and fairness, the EGF will be managed by a consensus-based committee, called the f(x) Open Market Committee (FOMC).

Summary

Time moves fast in the technology world and even faster in the blockchain space. Pundi X’s journey started in October 2017, slightly over a year ago, and we have been operating at a lightning pace ever since, making progress that can only be measured in leaps and bounds. We started as a blockchain payment solution provider and have evolved into a blockchain service provider to make blockchain technology more accessible to the general public, thereby improving your everyday life.
The creation of Function X was driven by the need to create a better suited platform for our blockchain point-of sale network and through that process, the capabilities of Function X have allowed us to extend blockchain usage beyond finance applications like payment solutions and cryptocurrency.
The complete decentralized ecosystem of Function X will change and benefit organizations, developers, governments and most importantly, society as a whole.
The XPhone prototype which we have created is just the start to give everyone a taste of the power of Function X on how you can benefit from a truly decentralized environment. We envision a future where the XPOS, XPhone and other Function X-enabled devices work hand-in-hand to make the decentralized autonomous ecosystem a reality.
You may wonder how are we able to create such an extensive ecosystem within a short span of time? We are fortunate that in today’s open source and sharing economy, we are able to tap onto the already established protocols (such as Consensus algorithm, FXTP, etc), software (like Android, IPFS, PBFT, Dockers, etc.) and hardware (design knowledge from existing experts) which were developed by selfless generous creators. Function X puts together, aggregates and streamlines all the benefits and good of these different elements and make them work better and seamlessly on the blockchain. And we will pay it forward by making Function X as open and as decentralized as possible so that others may also use Function X to create bigger and better projects.
To bring Function X to full fruition, we will continue to operate in a transparent and collaborative way. Our community will continue to be a key pillar for us and be even more vital as we get Function X up and running. As a community member, you will have an early access to the Function X ecosystem through the f(x) token conversion.
We hope you continue to show your support as we are working hard to disrupt the space and re-engineer this decentralized world.

Reference

Practical Byzantine Fault Tolerance
http://pmg.csail.mit.edu/papers/osdi99.pdf
Byzantine General Problem technical paper
https://web.archive.org/web/20170205142845/http://lamport.azurewebsites.net/pubs/byz.pdf
Global mobile data revenues to reach $630 billion by 2020
https://www.parksassociates.com/blog/article/pr-07112016
NPXSXEM token supply
https://medium.com/pundix/a-closer-look-at-npxsxem-token-supply-843598d0e7b6
NPXS circulating token supply and strategic purchaser
https://medium.com/pundix/total-token-supply-and-strategic-investors-b41717021583
[total supply might differ from time to time due to token taken out of total supply aka “burn”]
ELC: SpaceX lessons learned (PBFT mentioned) https://lwn.net/Articles/540368/

Full: https://functionx.io/assets/file/Function_X_Concept_Paper_v2.0.pdf
submitted by crypt0hodl1 to PundiX [link] [comments]

Potential Information

Potential Information
I'm going to try and demonsrate, in Natural Language, why there is a Revolution occuring in Information Science. The question I wish to Address is: "How much Information is there in a give Container?". As modern Computer Scientists see things, the amount of Information in a given container is precisely the number of possible discrete states of that conainer. So a nibble can be in 16 possibles states, a byte can be in 256 possible states, and so on. I'd to coin the term "Potential Information" and make an explicit Parallel with Potential Energy. So for a byte, the Potential Information is 256. It's interesting that we don't use Units for Potential Information, though it is a well studied concept, if newly named. Conctpetually, we understand the Units as 256 pieces of "Potential Discrete Information", so let us use name the Units pdi.
Let's extend the Parallel with Potential Energy. A Boulder at the Top of a Mountain is said to have a Potential Energy Relative to it's height, weight and the Gravitational Constant that is tranfered to Kinetic Energy if it Rolls down the Mountain. For Argument's sake let us Suppose a Flat Earth, then at the Bottom of the Mountain, the Boulder is said to have Zero Potential Energy (certinaly regarding its Potential to fall under Gravity but but I expect there are other ways Squeeze Enery out of Rock!). In a Computer I would say that a byte in a Switch On Computer is like the Boulder at the top of the Mountain with Maximum Potential Information (256pdi) and in a Switch of Computer, it has Minimum Potential Information.
So here's a Question first of all: "What is Minimum Potential Information?". Let's now do a thought experiment to help aswer the question at hand. Consider the concept of a "Broken Bit"; a bit that is fixed in either the 0 or 1 state and can't be changed. So, Information Theorists? What is the pdi of a Broken Bit? We now a working bit has 2pdi, but do we say the Broken Bit has 1pdi or 0pdi? 1pdi seems reasonable because it has a single Discrete State, but then 0pdi it seems we can't draw any information from it. If 0 is your answer, then I think you've jumped the gun, becuase I never told you what state it was locked in. What if I tell you it is locked in the 1 state? Well certainly we can draw no further information from it, but I say we still have the information that it is in the 1 state. So, I would say that before observation, the bit has 1pdi, but after observation, it has 0 pdi.
Now let us consider another possible unit of Information Measure "Discrete Information" or "di". So what is the di of a Broken Bit? Before we Observe it, we know we are going to read 1 Discrete Piece of information, and afterwards, we have read 1 Discrete Piece of Information. So I would say that the di of a Broken Bit is 1 in any Eventuality.
So you could interpret that as meaning that pdi is Time dependent and di is not Time dependent, which is a reasonable way to look at it. A more precise Way to look at it from a Computer Scientists point of view woud be to say that pdi is dependent on the number of "Reads" or "Potential Reads" where as di is not. This certainly holds for the Broken Bit. But, let us consider a working bit.
Let's get side tracked a bit and analyze a couple of common Computer Science Abstracts: Programs and Operations. Here's a suggestion for the definition of a "Program": A "Program" be an initial value for a container, and a series of well defined operations that manipulate the information of the container.
But this begs the question, what is an Operation... actually there's no obvious answer, it is thought of differently at different levels of the Computer Stack. To a user, Typing in a url and hitting Enter might be thought of as an Operation. The Web-Browser Software Developer, might consider an Operation to flag that the user has clicked in the url bar, an operation to read the string, operation(s) to analyis it, and operation(s) to send it to the DNS server. How about the guy who programmed the "String Read" operation, perhaps Scanf in C. That probably entails rather a few operations in Software alone, though it is a single operation in C. Then how many operations in Hardware were performed in this situation?
Here's a good Analogy for this type of thinking that any programmer will understand. Imagine you meansure Operations number of function calls. So how many operations in a "hello world application"? Well in C, it's One function call (not including main). Ok, but what about in Assembler? Rather a many function calls I would think. Then how did it get on your screen? Imagine the vast quatities of Function Calls that translate printf("hello world"); into a pattern of illuminated LEDs on the screen in a Terminal Window. Beyond that, how about the vast Edifices of Abstractions that lead to these LEDs glowing? Pixels, resolution, then colour of pixel which is represented as four bytes and needs Computer Software to interpret, then convert into a format correct to the monitor, then the monitor probably has more software to apply any colour correction and convert it into an Electrical Charge through some sort of Digital to Analog Converster that will eventually make a pixel glow with a certain colour. So how many operations in a "hello world" program? One could probably write countless Volumes analysing every operation that takes place from the flow of electrons through through Logic Gates, in the CPU, through the interupt mechanism on the chip to read you keystrokes, the abtraction of a bit and the operations of each ALU, the interpretation of the bits at each state of the ALUs computation etc. In fact, I think if you fully Analysed Everything that takes place inside a Computer in writing, compiling and executing a simple "hello world" program on a modern computer, you could probably chart pretty much the entire History of Computer Science.
For a moment, let us consider programs with no inputs, and et me suggest a definition of an Operation that may seem a little left field: "A Single Operation is the Space between two outputs", and "an output is any piece of information that it is a requirement that the program produce to satisfy its operation to the user". Let us assume for a moment that the only output device for a program is a Screen, and we a running a tech demo of the latest video game. As far as the user (i.e. viewer) is concerned, the only output they need is each frame. So long as the frame rate ticks over, the user is happy regardless of what is going on inside the computer. Then, the rate of Operations is Solely Dependent on how often the Screen updates, and 1 Operation takes place in the Computer inbetween each frame under this definition. So why use this seemingly bizarre Abstraction? What I'm seeking is an Absolute Measure of Compute Speed or Proficiency, and it seems to me, it is dependent on the program that is running. I'm sure those ASCII chips for mining bitcoin are dyamite at mining bitcoin, but your not going to get world of Warcraft running on them. I'm not sure you can really compare the Compute Speed of a ASCII bitcoin mining Rig to an XBox to example, certainly not simply by measuring Clock Speed and memory access rates anyway. What would be considered an "output" for a bitcoin miner? Hashrate is the standard measure of a bitcoin miners speed, and it is a most beautifully simple and perfect measure. Considering Compute Speed as "Numer of Operations per Second", then my definition of Operations and Outputs gives the Hashrate on a bitcoin miner. What about when an output is a frame on a Screen? Then on a game tech demo, for example, the Compute Speed would be the frame rate using the definitions I have already give. Again, probably the best know measure of Compute Speed for that type of Software. So perhaps I beginning to hit on a good generaization. I've actually conned you a little bit... in fact, under this definition of an operation as the "space between" outputs, my measure of compute speed of a video game is actually framerate-1 and my bitcoin mining measure is Hashrate-1. Here's another interesting consequence, with framerate, if my Computer is outputing a 30 frames per second, then I am running at 29 operations per second, but if I am running at 59 operations per 2 seconds... Actually very important with this measure of speed, which I'll write about another time. Those that have been studying O-Cycles may well have just spotted a Parallel! I want to consider another type of program also. Some programs (and in my opinion usually wise ones) don't necessarilly seek to operate as fast as possible. Take "metronome" program for example and let an "output" be one metronome "click". If you just tried to run it as fast as possible, you would have hyper speed noisy and irregular metronome. i.e. not really a metronome at all. So what would satisfy the user in a metronome program? Ignoring issues of software design, the main anwer would be accuracy of timing; usually not directly proportional to compute speed. Let us coin a new phrase, "Compute Proficiency" and say that for a metronome, Compute Proficiecy is measured by the accuracy of the metronome's timing. So Compute proficiency could be measured the deviation of the click, from some standar norm. i.e. deviation (perhaps in milliseconds) away from some target timing. Now, in my experience as a skilled bedroom music producer and Computer Scientist, this has precisely no relationship to the clock speed of any electronic/computer musical intrument I use. Consider measuring time in Beats and consider the Cartesian Plane with Time Measured on the x axis and Time Modulus 1 on the y axis. Then the beats will be series of points with y = around the line y = 0. Then we can do all sorts of Statistics to Measure Compute Profiency based on each point's deviation from (0, n) where n is an Integer...
[...a brief digression for those that have been following my other work, if we map the timing of each beat to the Complex Plane as follows: y = time and x = (time modulus 1) + 1/2, then let c = x + yi, then we have a rather recognizable line through the Complex Plane. For a Perfectly accurate Metronome, the line Re(c) = 1/2, i.e. what most think and hope are the Zeros of the Zeta Function... honestly, I'm still investigating whether this is True... I'm pretty sure that either the Sum of 0s divided by the number of Zeros Summed = 1/2 as i o-o, or they are all 1/2. Curiously, for the purposes I like to use this Science for, it wouldn't matter one jot which was True... So far anyway...]
So, if you'll exuse my digression, let's get back to measures of information. So I would propose the following definition of "rate of information": number of discrete pieces of information per output, with output defined per computer program. Let's take an example of Video playing software, and assuming so sound, say it out puts a grey scale image of 1024 x 1024 pixels every 100 milliseconds. Then assuming 1 byte per pixel, the program outputs 1 Megabyte memory per 100 milliseonds. So how much Discrete Information is it outputting per 100 milliseconds? Most people would say 1 Megabyte... How about per second? Again, most people would say 10 Megabytes. Here is how I would analyse the situation. I might say that a Megabyte, in a particular state, would constitute 1 Discrete piece of information (though not the only way of looking at it). Then I might day that the Potential Discrete Information of that Megabyte was 1024 * 1024 Discrete Pieces of information. So I would say the program is outputting at 10 Discrete Pieces of Information per Second- of course this doesn't consider Container Size of the Information. Let's look at it under a different lense, why would I consider 1 Megabyte in a particular state, a single piece of information? We could just as easily see it as 1024 * 1024 Discrete Pieces of Information if we consider the value of each pixel (byte) as a single piece of Information. Finally, I could consider it as 1024 *1024 * 256 Discrete Pieces of Information if we consider each bit individually. Here's a useful Equivolance Relationship:
Assume that the number of bits in a Sub-Container is a Power of 2 and the number of bits in a Container is a larger power of 2.
letting:
S = the Sub-Contain's Potential Discrete Information
C = the Container's Potential Discrete Information
s = number of bits in the Sub-Container
c = number of bits in the Container
then:
S / 2c = 2s / C
This is nothing to Computer Scientists, as Potential Discrete Information is what they usually consider. The above Relation is just a need formalization relating the number of bits and Potential Information in a Storage Container with a Sub-Container. Such as Total RAM to words or words to bytes etc.
Now what if we relate this to Discrete Pieces of information. Considering the situation, it seems that a single output should generally be considered a single Discrete Piece of Information. Then the goal of reducing the memory foot-print of Software Might be to make a Single Piece of Discrete Information have as little Potential Information as possible. How about an example: Consider out video game Tech Demo again, where we considered a single frame to be a single output and found that a single frame had 1 Megabyte of Potential Information. So by standard Information flow calculations, we are outputting information at 10 Megabytes per Second (One frame every 100 milliseconds). Now let's consider another situation, suppose we could stream a the output data to the screen without storing the whole frame. Let's say we could output it in 10 kilobyte chunks every 1 millisecond. Then our rate of information flow hasn't changed, however out memory footprint has reduced 100 fold. I'm still a little Wooly on the notion of an output, but it would now seem sensible to model an output as one of these 10 kilobyte chunks and therefore a discrete piece of information as a single output. So what do we have now:
1000 Discrete Pieces of Information per second 1 kilobyte of Potential Information per Discrete Piece of Information Therefore: 1 Megabyte of Potetial Discrete Pieces of Information per Second...
thus: Speed = pdi di/s
i.e Data Rate = Potential Discrete Pieces of Information per Discrete Piece of Information Per Second
So we may consider di/s purely a measure of speed of data trasfer, without considering size... e.g.
30 or 60 di/s for a 60 frames per second game for example, (treating each frame as 1 discrete piece of information). Then if it is outputting on 1024x1024 screen with 4 bytes per pixel, then we could say the Output Rate of the Game is:
Output Rate = 4Mb * 60 di/s or
Output Rate = 4Mb * 30 di/s
In visual Programs such as Graphical Programs, the di/s is VERY slow in comparison to a CPUs clock speed as humans rarely perceive quality improvements in animation about about 60fps (don't believe anyone who tell you that it's 30fps!).
Now consider the Polar Opposite in Modern Day Computing, a program than generates audio. an audio output device may ouput at 44,100 frames per second (for CD Quality) and the frames will usually be 16 bits for this kind of audio. So, such a pieces of Hardware/Software has the following output rate:
Output Rate = 16bits * 44,100 di/s
So some tell me, what is the Theoretical Minimum Memory footprint for such devices? The Theoretical Minimum is to create a program who's memory footprint is less that or equal to the Potetial Discrete Information Per frame. That doesn't help you with how to achieve this, but you certainly could not beat that minimum. I'm in the process of designing programs that can do this kind of this using the Tick operation.
Now, what's the minimum Discrete Pieces of Information per frame. The Answer is actually very Surpising, even for interesting programs. The answer is 1 bit. Let me explain. EVERY output of a Computer is Analog bar none. Very obviously so in Audio Devices and and old Televisions, but even Digital Information transfer is a Wave that is interpreted Digitally. Now how many bits does it take to produce a Wave? Well let's say I flick a bit at 500Hz and output it down a cable and send it into an Amp. Then I've just created a 500Hz Square Wave and I didn't need any software to Store anything, interpret what was stored, convert to packets, decode and send to the audio device. I wont speak much more about this now because I lack the Language of an Electrical EngineeEnergy Scientist to Describe my supositions, but one thing I do know, from an information persective, is that you can generate a Vast Quantity of Waves simply by flicking a single bit with the correct timing and sequence. Finally, when it gets to the point of directly outputting an Analog Signal direct from Code, what does this Discrete Pieces of Information per Second thing mean that I'd talking about earlier? You might say that the speed was the rate at which we flicked the bit, which is probably reasonable, but by the same token, the output itself does not have a discrete quality if it is a smooth Wave...
Here's the idea... you know those ugly annoying Computer Noises that sometimes leak from Speakers, like the Insidious Machinations of some Digital Monster? That is the Amplified noise of a Computer's Brain Pattern. We send that brain Data, our Digital Firend Mulls it over using His/Her Digital Brain Wave, then sends us back data. My thinking is to try to manipulate the Computer's Brain Waves Directly, then Amplify the result to use for whatever purposes...
Finally, what happens if you amplify the signal of [a] bit[s] ‘ticking itself in an O-Cycle? That’s kind of where I’m going with this...
...hmmm... Mysterious...
Nishikala
submitted by PotentiallyNishikala to mathematics [link] [comments]

Bitcoin Price MAYHEM! What you need to know... (Crypto Over Coffee Ep.8) BITCOIN: Thinking About Selling NOW? FIRST You NEED to See This Chart! MIND BLOWING! Bitcoin Prices News Explained - $100,000,000 BTC Purchase By Mystery Whale - Who Was It? GOOD NEWS for BITCOIN! Money Flood Bringing MASSIVE Bull Run [INSANE] Bitcoin Halving - NOT PRICED IN! [100% Gains coming]

This structure contains some fields that are shorter than a byte (octet), e.g. the version field is 4-bits wide (aka a nibble) Ninja recieves a 10,000 bit donation - how much is this worth? Twitch Bits to US Dollar Calculator. What is the Value of a Twitch Bit Bits manipulation (Important tactics). In the book I've learned that a nibble = 4 bits, 8 bits = 1 byte next is a word - which is usually in groups: 8 bits, 16 bits, 32 bits or 64 bits (so on), and all this makes perfect sense to me. Here's my homework question which is kind of confusing to me: "A computer has 64 MB of memory, Each word is 4 bytes. How many bits are needed to ... Thus, one eighth of eight-reales became one bit, one quarter two-bits–the equivalent of our present day quarter-dollar. One-half is four-bits and three quarters are six-bits. Many believe these ... Task. Write a program that takes a bitcoin address as argument, and checks whether or not this address is valid.. A bitcoin address uses a base58 encoding, which uses an alphabet of the characters 0 .. 9, A ..Z, a .. z, but without the four characters: If a character is 8 bits, or 1 byte, then a WORD must be at least 2 characters, so 16 bits or 2 bytes. Traditionally, you might think of a word as a varying number of characters, but in a computer, everything that is calculable is based on static rules. Besides, a computer doesn't know what letters and symbols are, it only knows how to count numbers. So, in computer language, if a

[index] [36599] [13458] [12730] [14645] [3414] [26053] [28305] [31371] [20871] [1905]

Bitcoin Price MAYHEM! What you need to know... (Crypto Over Coffee Ep.8)

"In time of deceit, telling the truth is a revolutionary act." G.orwell Welcome to Bittruth (bit too official xD) where we share cryptocurrency and bitcoin c... Episode 1 : Bitcoin Series In this video I teach you how to install a digital wallet to contain your Bitcoins. I also teach you how to utilize the Bitcoin Faucet to get your first free coin. How much Bitcoin do you actually need to get rich? How much Bitcoin for financial freedom? ABRA - GET $25 IN BTC - (US bank deposits or AMEX)- https://invite... The Bitcoin halving is not priced in according to famous analyst, Bitcoin is going to see 100% gains coming! Also the NY FED reminds us all why banks suck. Watch more awesome crypto news here ... #Bitcoin panic is slowly spreading as many fear a major correction is near. ... This video, description and/or comments may contain affiliate links. By utilizing any of the these links you are ...

#