Jump to content

Vokez

Member
  • Content Count

    9
  • Joined

  • Last visited

  1. https://sydcharts.io A charts web site is now available which gives a basic perspective on the SystemD Network, including Account Explorer and Transactions. We will be adding more features to the site as the network becomes more active and has more data that can be represented.
  2. The subject of the possibility of transaction replay attacks came up as a topic in a different thread. It was suggested that, theoretically, valid transactions on the Ripple Network couple be resubmitted as valid transactions on the SystemD Network. The opposite was also suggested, that valid transactions on the SystemD Network could be accepted as valid transactions on the Ripple Network. I discussed this theory with my colleagues. We came up with two different approaches to preventing these replay attacks. If someone, maybe even @Sukrim or @at3n, were able to actually perform a replay attack, and show us the transaction in both the SystemD Ledger and the Ripple Ledger, then it would be of great help. Not only would it prove the theory that replay attacks are possible, but also it would give us more insight as to which approach we should take to prevent them.
  3. Vokez

    Ripple Network forked to create SystemD

    Hello @Sukrim It is unfortunate that I was not able to answer your questions in time to give you a better impression of our projects. I remember reading your posts in the early days of the original forum @ ripple.com, long before xrpchat even existed. You always shared very knowledgeable perspectives. In either case, I'm sure that in time you will change your opinion about our projects.
  4. Vokez

    Ripple Network forked to create SystemD

    Hello @jargoman Thank you for your input. No, it is currently impossible to create a valid transaction on the Ripple Network and then resubmit the same transaction on the SystemD Network. At the time of writing, the Ripple Network is on ledger #44,399,043. The current ledger number on the SystemD Network is #44,418,803 The SystemD Network is almost 20,000 ledgers ahead of the Ripple Network. Therefore, any transaction that is valid on the Ripple Network can never be valid on the SystemD Network. The "LastLedgerSequence" would always make the transaction invalid. Even if, by some miracle, both networks were on the same ledger number, at the same time, the transaction would still be invalid because of the "Sequence" value of the transaction. As the Ripple Dev Portal explains: "A transaction is only valid if the Sequence number is exactly 1 greater than the previous transaction from the same account." https://developers.ripple.com/transaction-common-fields.html So a second miracle would need to happen in order for the "Sequence" of the sending account to be the same on both Networks. Even if two miracles happened and both Networks were on the same ledger number, at the same time, and the same account on BOTH Networks contained the the same "Sequence" number, you would still need a third miracle to have both Networks expecting the same "AccountTxnID" from the sending account. https://developers.ripple.com/transaction-common-fields.html#accounttxnid These security measures are just one of the many examples of the superiority of Ripple financial technology, in many areas, over most of the open source financial technology that exists today. If we are successful in our endeavours, then they will bring Ripple Technology to even more people and we will see it used in ways that it has yet to be used.
  5. Vokez

    Ripple Network forked to create SystemD

    Hello @lucky , Thank you for your responses. The Ripple Network has been forked and the SystemD Network was created as a result of the fork. There is no question that the Ripple Network and the SystemD Network are physically two different networks that are not connected to each other. Although, both networks have a common history. Anything that happened on the Ripple Network before January 11, 2019, also happened on the SystemD Network. Anything that has happened on the Ripple Network since January 11, 2019, did not happen on the SystemD Network and vice-versa. Two completely different networks that have a common past can only happen as a result of a classic "fork". SystemD is a "parallel network", as defined in the Ripple Dev Portal: "When different consensus groups of rippled instances only trust other members of the same group, each group continues as a parallel network." https://developers.ripple.com/parallel-networks.html
  6. Vokez

    Ripple Network forked to create SystemD

    @jargoman Which URL and port? We can take a look to see if there is an issue.
  7. Vokez

    Ripple Network forked to create SystemD

    @Warbler No, am not familiar with DanielW or his project.
  8. Vokez

    Ripple Network forked to create SystemD

    Hello Pablo, Thank you for your reply and thank you for your questions. If there is any part of my answers that you do not understand, just let me know and I will try to explain again. This is actually a two part question: who the developers, and who are the owners. Vokez is a multinational group of developers and other talented people who have decided to create the security token platform called The State We have been working on the idea and developing prototypes to test our design theories for over a year now. We so strongly believe in the potential of security tokens, that we decided that we would use the The State as a tool for the organization, incorporation, and direction of Vokez the Company. This brings us to the answer of the second part of your question, who are the owners of Vokez? The owners of Vokez are the people who join Vokez by making a security token purchase, the founders of Vokez, the rest current Vokez team, and some future employees. By using security tokens as a representation of ownership in Vokez, the ownership of Vokez will be divided in the following manner: - 60% of ownership will be held by those who join Vokez via our STO (Security Token Offering) - 20% of ownership will be divided by the founders of Vokez - 10% of ownership will be divided amongst the rest of the member of the current Vokez team - 10% of ownership will be designated to future employees of Vokez the Company. They are the Owners. Our security token platform will allow issuers to select the jurisdiction in which they are operating and the local regulatory standard under which they would like to issue the security tokens. Based on their selections, our platform will present them with the ability to configure their security token, but only within the limits and guidelines of the local regulatory standard that they have selected. For example, if an organization wanted to perform fundraising in accordance with a local standard which only allowed them to raise a maximum of 1 million, then our platform would only allow them to issue the tokens if the number of tokens multiplied by the price per token was under 1 million. By using our security token platform, The State, anyone can issue security tokens in accordance with their local regulations and standards in order to legally raise funds. So, as you can see, yes, our security token platform will empower companies, projects, and organizations with the ability to legally raise funds. In order to understand the answer your questions (A), (B), and (C), you must first understand what a security token is, then you must understand how The State is different from most of the security tokens platforms out there. I am sure that you already know that a "security" is defined by the 4-part “Howey Test”: it’s an investment of money, in a common enterprise, with an expectation of profits, solely based on the efforts of others. A "security token" in it's simplest form is basically a digital representation of a security as defined by the Howey Test. So how does that translate into the fledgling world of crypto-currencies? Well we all know what a token is: it's digital and it can be transferred from one person to the other. A security token is also a digital token also, but it has AML/KYC on the token itself. Each security token has it's own white-list of people who can legally receive a transfer of the token or posses the token. This is the standard implementation of a Security Token 1.0. Our security token platform, The State, is a Security Token 2.0 platform. This means that not only does the platform allow for the issuance of tokens and granular control of who can possess the tokens, but it also contain 4 extra functions: voting, privacy, derivatives, and off-chain data access. The function that concerns the answer to your questions (A), (B), and (C), is voting. Our security token platform has voting built-in to the token. That means that as soon as our Security Token offering ends, these security tokens will begin to be used for establishing Vokez the Company. All decisions, such as, where the company will be established, and what jurisdiction will it be operating in, and all major decisions about the direction of the company will be made by voting through the security tokens. All decisions will be made the Owners, and the Owners are the people who possess the Vokez security tokens.
  9. The Fork We are very proud to announce that we have successfully forked the main Ripple Network in preparation for providing functionality for our security token platform called "The State". More information about The State is available at: https://vokez.io/platform.html This is a first hard fork of the Ripple Network and it is called "SystemD". The fork was performed around 0:05 GMT on January 11th, 2019, around ledger number 44317418. Just as with hard forks of blockchain based currencies, any one who possessed "XRP" on the main Ripple Network at the time of the fork now possesses "SyD" on the new SystemD Network. The Parallell Network SystemD is the first parallel network. https://vokez.io/systemd.html Being a parallel network means that all existing wallets, APIs, libraries, and other applications that work on the Ripple Network will also work on the SystemD Network. The only configuration change that is necessary is simply replacing "ripple.com" with "vokez.io". For example, many wallets use the servers "s-east.ripple.com" and "s-west.ripple.com". To use the same wallet on the SystemD Network, you would simply change the servers to "s-east.vokez.io" and "s-west.vokez.io". Our Goals The way that the current Ripple Network is structured today, you need to make a serious investment in servers and network resources if you want to participate on the network. This creates a high barrier of entry for anyone who might consider participating on the Ripple Network. One of our goals is to lower the barrier of entry of Ripple financial technology. There are enhancements that we will be implementing that will make it easier for the common person with common hardware to participate on the SystemD Network. For example we will be storing historical transaction data in a public distributed hash table. Then no one will need to store the whole ledger history. It will be collectively stored by all participants on the SystemD Network. Each person will only need to hold a small portion. We want to exploit the massive potential of Ripple technology in a ways that have direct, positive effects on everyday people. One example of this is using SystemD to provide transaction processing for The State. The State is a security token platform that will empower companies, projects, and organizations with the ability to legally raise funds in accordance with local and international regulations. Transactions and other functions requiring consensus will be part of the sphere or functionality (SoF) that SystemD will be providing to The State. Read more: https://vokez.io/systemd.html#spheres-of-functionality Another goal of ours is to implement a new currency distribution program. The first step of the SystemD currency distribution program is to nullify all of the largest wallets. Another aspect of this program is to give all registered members the opportunity to receive a daily stipend of 120 SyD. The Network Our two main xts-rippled servers are: - s-east.vokez.io:443 - s-west.vokez.io:443 Our three main validators are: - val-east.vokez.io:51235 - val-west.vokez.io:51235 - val-r.vokez.io:51235 Run an xts-rippled server: Github: https://github.com/VokezOfficial/xts-rippled Docker: https://hub.docker.com/Vokez docker run -d --restart=always -p 51235:51235 \ -p 5001:5001 -p 8080:8080 vokez/xts-rippled:latest Social Twitter: https://twitter.com/VokezOfficial
×