Personal Console - DYNAMIC ALIAS

Community Cluster PERSONAL CONSOLE
1

DYNAMIC ALIAS Menu

dynamic_alias_menu

Nodes

dynamic_alias_nodes

Three sets of Node are available and they all have identical submenus. Node Set defines the Node used and by default, Node Set A is the active node in use.

Tree Listing

DYNAMIC ALIAS is divided into 4 categories:

  1. Alias List
  2. Alias Details
  3. Alias Phone
  4. Alias Verification
  5. Alias Keys

1. Alias List

A fundamental feature of Private Cyberspace is the protection of your privacy by enabling you to create different Aliases for yourself for different situations.

There are 3 alias types available:

  1. Private Alias - use to collect data only (no sending out).
  2. Guest Alias - use to send fuzzy data anonymously.
  3. Member Alias - use to send fuzzy under progressive identity protection.

Private Alias

It comes by default with a Private Alias which you can use to collect your first data PRIVATELY.

Guest Alias

To upgrade to Guest Alias, click on DYNAMIC ALIAS -> Alias List-> Create Alias and follow the prompt. During this process, a Wallet is also created and there are 5 different types of Wallet, the more keys the more secure.

If any of the 3 keys is selected, the wallet will be created automatically.
If 4 keys is selected, one External Key Setting is required.
If 5 keys is selected. two External Key Settings are required.

Please wait until the Wallet creation completed message is displayed as this process will take a couple of minutes.

wallet_type

If the alias is downloaded, it can be re-used by importing the alias back.

Member Alias

To upgrade to Member Alias, click on DYNAMIC ALIAS -> Alias Verification -> Phone Number - Call In -> Enter the mobile number -> Register. Please ring 138813 within a minute using the mobile number entered and a phone number verified voice prompt will be played if successful.

If the alias is downloaded and saved, it can be re-used by importing the alias back.

2. Alias Details

This is the place to enter your personal details, such as Display Name, Phone Number, Email address etc.

3. Alias Phone

Under Development

4. Alias Verification

4.1 Identity Verification

Some transactions cannot be performed if you remain anonymous by using Guest Aliases.

By performing Identity Verifications, you can attach verified identities to some of your Guest Aliases and turn them into Member Aliases.

Currently 8 levels of verifications are supported for Member Aliases in the Australian Ecosystem :

  1. Phone Number - Call In
  2. Primary ISP - Browser Agent
  3. Email address - Mail Out
  4. Charge Card - Credit Card
  5. Phone Number - SMS Out
  6. Identity Card - AU Medicare Card
  7. Photo Card - AU Driver Licence
  8. National Passport - AU Password
level type prefix description
aupass_ Australian Passport
aumedi_ Australia Medicare Card
aupass_ Australian Passport
auactdrv Australia ACT Driver License Number
aunswdrv Australia NSW Driver License Number
auntdrv Australia NT Driver License Number
auqlddrv Australia QLD Driver License Number
ausadrv Australia SA Driver License Number
autasdrv Australia TAS Driver License Number
auvicdrv Australia VIC Driver License Number
auwadrv Australia WA Driver License Number
level type prefix description
0 Primary ISP - Web Browser auisp_ Australian ISP
1 Phone Number - Call In auphone_ Australian Phone

You can use Member Aliases at different levels in different situations. Some applications (e.g. withdraw money from a bank) has Member Alias level restrictions - so you cannot use those application if you at a lower level.

If you are not an Australia resident or citizen you most likely can only go up to level 4.

4.1.1 Phone Number - Call In

Before the other types of identity can be verified, It must always start with the first one which is the phone number. Once the phone number has been verified the verification date will be shown and the alias will change to Member alias.

If successful, a Verification Token will be displayed on the Alias Verification page and a grey_marker pin will be added and shown on the map.

Note: in order to save the new Member alias to a local disk (mobile phone storage location), to a remote server or to both, please enter the Member alias password and follow the prompt.

4.1.2 Primary ISP - Browser Agent

To verify your web browser, simply click on the Submit link and the Current ISP, Current Agent and Current Hash will be displayed.

If the Publish to Hub is ticked, the verification confirmation is also published on https://hub.contacttrace.com.au/@identity
.

4.1.3 Email address - Mail Out

Enter your email address and click on the Get Code button. Please check your email to get the code and enter it to verify your email address.

If the Publish to Hub is ticked, the verification confirmation is also published on https://hub.contacttrace.com.au/@identity .

publish_to_hub

4.1.4 Charge Card - Credit Card

Enter your credit card details and a small amount will be charged. Please check your credit card statement and enter the amount charged (less than $1.00) to verify your credit card.

If successful, a Verification Token will be displayed on the Alias Verification page and a grey_marker pin will be added and shown on the map.

If the Publish to Hub is ticked, the verification confirmation is also published on https://hub.contacttrace.com.au/@identity .

4.1.5 Phone Number - SMS Out

Under Development

4.1.6 Identity Card - AU Medicare Card

Enter your Medicare card details and click on the Submit button. The details submitted will be checked using the Document Verification Service (DVS) and if the details are entered correctly, the Medicare card will be verified.

If the Publish to Hub is ticked, the verification confirmation is also published on https://hub.contacttrace.com.au/@identity .

Note: credit card must first be verified.

4.1.7 Photo Card - AU Driver Licence

Enter your Driver Licence details and click on the Submit button. The details submitted will be checked using the Document Verification Service (DVS) and if the details are entered correctly, the Driver Licence will be verified.

If the Publish to Hub is ticked, the verification confirmation is also published on https://hub.contacttrace.com.au/@identity .

Note: credit card must first be verified.

4.1.8 National Passport - AU Password

Enter your Passport details and click on the Submit button. The details submitted will be checked using the Document Verification Service (DVS) and if the details are entered correctly, the Passport will be verified.

If the Publish to Hub is ticked, the verification confirmation is also published on https://hub.contacttrace.com.au/@identity .

Note: credit card must first be verified.

4.2 Location Verification

4.2.1 Night Block

Night block stores the Local Block Latitude and Longitude.

4.2.2 Day Block

Day block stores the Global Block Latitude and Longitude.

4.2.3 Local ISP - Browser Fingerprint

If successfully verified, the Client Fingerprint and the Server Fingerprint will both be displayed.

4.2.4 Venue Owner

A user with Member alias can verify a venue location as long as the phone number entered is a valid one that is recognised publicly and the correct code sent to that phone is entered.

In the example below, the venue is Marigold Restaurant and the phone number where the Code will be read out is 61292813388. If the correct code is entered, the venue will be verified.

venue_owner

4.3 Check Verification

By clicking on the Search button, the relevant details will be shown.

localblock

In the example below, the Local Block is compared to the data on the blockchain.

localblock_matched

4.4 Show Verification

Select this to view the verification details which have been submitted to https://hub.contacttrace.com.au/@identity

4.5 Verification Log

It shows the verification history such as the date, the time and the verification type.

5. Alias Keys

All aliases come with at least 4 keys:

  1. Public encryption key
  2. Private encryption key
  3. Public signing key
  4. Private signing key

5.1 Encryption

encryption

Encrypt

The Encrypt button is used to encrypt the data entered in the Input Area box. In order to send an encrypted data, the sender needs to:

  1. Get the Encrypt Key of the receiver and paste it by clicking on the Encrypt Public Key button.
  2. Type the message in the Input Area box and click on the Encrypt button.
  3. Copy the data shown in the Output Area and send it to the receiver.

Decrypt

The Decrypt button is to view the encrypted data received:

  1. Copy the data received and paste it in the Input Area box.
  2. Click on the Decrypt button
  3. The decrypted data is displayed in the Output Area box.

Sign

This utility is to create a signature within the contacttrace.com.au domain. Type the characters in the Input Box, click on the Sign button and the signature will be displayed in the Output Box.

In the example below, the signature is
r8hZHZO9lUNUprOS1235_Bszx1Er3CfS9hjd4S7QZfzV07EosFEChmoAWIqiI-s_3ZemHTPlFoHNXJiH44vUCw

sign_test

Verify

This utility is to check the signature created within the contacttrace.com.au domain. Click on the Verify button, type or paste the signature in the pop-up window and click on the OK button.

In example below, the signature above which is r8hZHZO9lUNUprOS1235_Bszx1Er3CfS9hjd4S7QZfzV07EosFEChmoAWIqiI-s_3ZemHTPlFoHNXJiH44vUCw
is verified.

verify_test

Copy to Clipboard

Copy the highlighted data from the Input Area or Output Area box to the clipboard.

Encrypt Public Key

The Encrypt Public Key button is for the sender to enter the public key of the receiver so the data sent to the receiver can be decrypted and viewed by the receiver.

Verify Public Key

The Verify Public Key contains the receiver's public key that can be shared to the sender which needs to be included by the sender before encrypting the message.

5.2 Hash

This utility is for transforming any given key or a string of characters into another value as in the example below.

alias_keys_hash

3

Alias Keys

All alias comes with at least 4 keys:

  1. public encryption key
  2. private encryption key
  3. public signing key
  4. private signing key

Public Key Pairs

By default the Public Key Pairs are NaCl based:

Public Key Demo

Secret Keys

By default the Secret Keys are NaCl based:

Secret Key Demo