Support and Documentation

• Getting Started with TrxSys (An introduction)

• Learn About Blockchain

• TrxSys.net Blog and Community

• How to: Create a Basic Transaction "Hello World!"  

• How to: Create a Simple Chain App on TrxSys  

• How to: Run a TrxSys Proof of Concept  

• Understanding the TrxSys Transaction

• TrxSys API and SDK

• TrxSys Technology

• Common Conventions

• Transaction Inspector
  (use to check that a transaction is valid)

• Encoding

• Registering a Chain App ID

• TrxSys Governor Public Keys

• Decrypt Private Key

• Authoritative Domains
  (How to have domain be verified in Chain Apps)  

TrxSys

TrxSys is designed to be used. To that end we have made the system very easy to use. TrxSys is for people and businesses.

TrxSys is not an investment cryptocurrency. It will not go up in value. TrxSys cryptocurrency is used to make transactions across TrxSys ecosystem easy and dynamic.

The first step is to register. Click the menu icon then select Registration. The registration process is fairly similar to most any web service. There is a fee to register, but that fee includes sufficient TrxSys cryptocurrency to get started.

TrxSys Technology is called ChainCasting

TrxSys represents a significant leap forward for blockchain technology. Our technology includes:

Distributed Ledger Technology (DLT) becomes Multiplexed Ledger Technology (MLT). MLT uses a patent pending technology to multiplex signature arrays within a common ledger to essentially virtualize an infinite set of sub-ledgers. This enables very granular control, attestation and definition of related transaction sets. Additionally, ledgers do not need to be distributed to many nodes in order for universal trust to be established.

Decentralization becomes authoritative portability. With authoritative portability, enabled by Multiplexed Ledger Technology, a user can redirect access control to specific transaction sets. The benefit is that a user will be able to choose a new bank, ecommerce site, social media provider, insurance carrier, whomever, by simply selecting a new one. Transations become user-centric versus the existing model of institution-centric.

Multiple additional features within the TrxSys ChainCasting system make blockchain practical. Attributes of TrxSys ChainCasting include: high performance, compliant to GDPR/HIPAA/CCPA, anonymous, reasonable transparency, authoritative portability, anti-fraud, anti-forking, very low cost, predictable cryptocurrency fees/valuation, defined governance model, blocks are redefined to only contain a single transaction, transactions are extended in functionality, and more.

Common Conventions

Rounding

Rounding uses Round Half to Even at .00001 position (decimal or five significant figures) in all cases where a calculation is performed or data is stored.

Examples:

• -2.14971313792379 rounds to -2.14971
  
• -1.86093194267841 rounds to -1.86093
  
• -0.712145015514913 rounds to -0.71215
  
• -1.17901520893561 rounds to -1.17902
  
• 9.99308217212349 rounds to 9.99308
  
• 4.77936475523151 rounds to 4.77936
  
• 7.45880227905527 rounds to 7.4588
  
• -2.27925293887061 rounds to -2.27925
  
• 6.16237790315072 rounds to 6.16238
  
• 8.18933032046289 rounds to 8.18933
  
• 3.1234555 rounds to 3.12346
  
• 3.1234505 rounds to 3.12345
  
• 3.5 rounds to 3.5

During the initial roll-out of TrxSys the maximum transaction size will be 10MB. We will increase the size at a later date.

Encoding and Data Sanitation

Encoding of free form fields

All free form text fields will be encoded to Base64. Even though the message field is encrypted the message will be base64 encoded and then it will be encrypted. This done to keep users safe (and TrxSys). A risk is presented to users if raw messages are displayed with risky code in a message or other free form field.

Sanitation of free form fields

Many free form text fields will be sanitized to reduce the risk of malicious code executing. In such cases that field sanitation is used then a note will appear djacent to the field to inform the user.

Registering a Chain App ID

Chain App Registration

A sender_chain_id must be established with a transaction type 2. This is used to open a sender_chain_id. Without this function then it becomes questionable as to when a Chain App ID was established. Therefore, any transaction other than type 2 will require that the sender_chain_id be confirmed as existing and valid.

How to create a Chain App ID

The easiest way to properly register a Chain App ID (formally called sender_chain_id) is to use the Create Chain App form at [Create a Chain App]

Learn more about creating Chain Apps [Learn about Chain Apps]

Instructions on creating Chain App ID for API use [How to Register a Chain App ID]

Published Public Keys of TrxSys Governor

Every transaction is signed by the centrally controlled governor process. Below is the governor's public key. Eventually there will be many published public keys.

As a reminder, never publish your private keys.

-----BEGIN PUBLIC KEY-----MIH1MIGuBgcqhkjOPQIBMIGiAgEBMCwGByqGSM49AQECIQD////////////////////////////////////+///8LzAGBAEABAEHBEEEeb5mfvncu6xVoGKVzocLBwKb/NstzijZWfKBWxb4F5hIOtp3JqPEZV2k+/wOEQio/Re0SKaFVBmcR9CP+xDUuAIhAP////////////////////66rtzmr0igO7/SXozQNkFBAgEBA0IABI8Cs7hXNyXooEOSIasg6rIYbmeDPRkAcOCIFmPkb6NxDDb6arn9AcZZDb6FpxF1Q1aCw/IJAgMGxI58HlODyOY=-----END PUBLIC KEY-----

The governor's public key can be accessed as a text file at:
governor_public_key_1.txt  

How to decrypt private key

Decrypting the private key

The private key is encrypted via AES. Your keys can be found by going to Menu >> My Account. You will see that your public key is clear text (unencrypted) while the private key is encrypted. To keep your private key safe it is encrypted based on a password (a key) derived from a hash of your TrxSys password. The following is a Perl script to show you how to decrypt your key. You can use this program. Simply install Perl, the requisite modules and then copy your keys exactly as they appear in the My Account page.

### Decrypt private key. ## September 30, 2019 ## Robert Vaughn ## TrxSys.com ## User Documentation use Digest::SHA qw(sha256_hex sha256_base64); use Crypt::PK::ECC; use MIME::Base64; use strict; use warnings; ### TrxSys encrypts private keys using a derivative of the user's TrxSys password. ### This program provides an example of how to use Perl 5 to decrypt a private key. ### Do not share or otherwise disclose your private key or password. ### User credentials ## login ID is not required my $lg_password = 'thisisapassword003'; ### Keys copied from Account page ## The primary key is encrypted ## The public key is not encrypted my $primary_priv_key_aes = '{key_index:"y9OkjYfQ"|iv:"pk7azoSGRF7yTftd"|private_pem:"35b613ff9546f9c21c05b06f4fe64e4301ced1614a67383d17fecf08a4c7bf34cf0301294aba0361398cf02dcd9d7854c7ba253a672ed1e054ea0a2f6e2937f1467ed261649ec746a74ce7776ad84166dfa76eb81f6371eb7775d361a16fa45ba4c1ee4a19e298c2f1c76099ced1a32a5d972d85f9b7bfaff1e5511f0a9789e1a9b625e0072c1707a8cac24d026560d02d76a4cdcd89fe8afba29f4fdab5c13c0f25765758221de0b28d948a3b3d432eb3edc071f2c6b4aeb09d91ab1a510e5dd502e4610fd6b3cc02a3c80c99bedd5cbedb936d856efd9381ad0da3af8ab983d0d241bdccc3c52567ac974a3dd9b891979fac527e41472d843493bed2b40a6d3371d40f910ac6c47222c87b6f048aa34a677c00566df027df7780a5392ca3904efa781873c4e92754d5431be691d4bd88afe6460a451827e05f27f06a25aba176d662b703b83e66561df861623adbb58a6e0c0a4adc932126851b16ed4fcc502e9d60f0a7556602b54b0a8ecb45a0e01e0145e91340105f261b6f9d7ba87aa7ae488163d7b5ea0ce414bd2b8ab41b23fb3a263d367c8816835dc52fcd5752fdf0f1c6ad52fdb711797a8898260b1257"}'; my $sender_pkp_public = '-----BEGIN PUBLIC KEY-----MIH1MIGuBgcqhkjOPQIBMIGiAgEBMCwGByqGSM49AQECIQD////////////////////////////////////+///8LzAGBAEABAEHBEEEeb5mfvncu6xVoGKVzocLBwKb/NstzijZWfKBWxb4F5hIOtp3JqPEZV2k+/wOEQio/Re0SKaFVBmcR9CP+xDUuAIhAP////////////////////66rtzmr0igO7/SXozQNkFBAgEBA0IABOn1sQ0UCS96NLyNR7OEVOkDmI3tcVpCgKC4YD+cFAiYHF6I/9RKycVBP2NPpqJkptAGHAIUzlTgtwTtjMhQklc=-----END PUBLIC KEY-----'; ################################################# ### Decrypt string with primary_priv_key_aes ## Parse primary_priv_key_aes atring my ($sender_pkp_iv) = $primary_priv_key_aes =~ /iv:"(.*?)"\|/; # IV is initialization vector my ($sender_pkp_private_aes) = $primary_priv_key_aes =~ /private_pem:"(.*?)"/; ## IV was included in encrypted private key string. The key is derived from first 32 characters of hash of lg_password my $hash_of_lg_password = sha256_base64($lg_password); my $sender_lg_password_key = substr($hash_of_lg_password, 0, 32 ); my $sender_pkp_private_aes_bin = pack "H*", $sender_pkp_private_aes; #convert hex back to binary my $cbc_s = Crypt::Mode::CBC->new('AES'); my $sender_pkp_private = $cbc_s->decrypt($sender_pkp_private_aes_bin, $sender_lg_password_key, $sender_pkp_iv); print "encrypted private key string = $primary_priv_key_aes \n\n"; print "iv parsed from encrypted private key string = $sender_pkp_iv\n\n"; print "encrypted private key = $sender_pkp_private_aes \n\n"; print "password key derived from user password = $sender_lg_password_key\n\n"; print "decrypted private key = $sender_pkp_private\n\n"; print"sender_pkp_public = $sender_pkp_public \n\n";

---