viklas

Instructions to workaround issue with Parity wallet transferring tokens purchased during ICO (tested on Mac)

PROBLEM: Investors who purchased MCO (Monaco) tokens during the ICO, using a Parity wallet, face an issue transferring those tokens. It appears that parity is failing to automatically create a new ERC20 token (let's called it NMCO) after Monaco performed a 'token reissuance' after the ICO closed, but before it was listed on Bitrex (untransferable period). As a consequence, all attempts to send MCO tokens (purchased during ICO) from Parity to Bittrex fails. This is presumably because the tokens Parity is trying to send are the 'dead' MCO tokens, not the new 'NMCO' tokens.

This process allows a user to send 'NMCO' tokens to Bittrex for trading. NOTE: Parity still does not show the 'NMCO' tokens, even though the transaction has defintely worked.

1. Backup Parity keys to file from terminal (creates zip file on desktop) - STORE THEM SOMEWHERE SECURE (don't recommend leaving on desktop)

$ cd $HO

viklas

Keybase proof

I hereby claim:

• I am viklas on github.
• I am lukebenson (https://keybase.io/lukebenson) on keybase.
• I have a public key ASAThD-CpYAitkJKDMo2D5lIsrs05ouvmosG712dGvTpGQo

To claim this, I am signing this object:

viklas

time="Aug 15 11:26:55" level=info msg="Starting Poller"
time="Aug 15 11:26:55" level=info msg="Setting up Server"
time="Aug 15 11:26:55" level=info msg="--> Standard listener (http)"
time="Aug 15 11:26:55" level=info msg="Registering node."
time="Aug 15 11:26:55" level=info msg="Node registered" id=8606858c-2eff-47d1-4995-5b1f8db438f7
time="Aug 15 11:26:55" level=info msg="Starting heartbeat."
time="Aug 15 11:26:55" level=info msg="Detected 4 APIs"
time="Aug 15 11:26:55" level=info msg="Loading API configurations."
time="Aug 15 11:26:55" level=info msg="--> Loading API: XXXXXXX"
time="Aug 15 11:26:55" level=info msg="----> Tracking: (no host)"

viklas

FROM nginx
ADD dist /usr/share/nginx/html

viklas

<div id="chartContainer">
  <script src="http://d3js.org/d3.v3.min.js"></script>
  <script src="http://dimplejs.org/dist/dimple.v2.1.2.min.js"></script>
  <script type="text/javascript">
    var svg = dimple.newSvg("#chartContainer", 590, 400);
      d3.tsv("/assets/data/example_data.tsv", function (data) {
        dimple.filterData(data, "Date", "01/12/2012");
        var myChart = new dimple.chart(svg, data);
        myChart.setBounds(60, 30, 420, 330)
        myChart.addMeasureAxis("x", "Price");

viklas

{
    "apiVersion": "v1beta3",
    "kind": "ReplicationController",
    "metadata": {
        "creationTimestamp": null,
        "labels": {
            "name": "logging"
        },
        "name": "logging",
        "namespace": "AAAAAAAAAAAAAA"

viklas

##Instructions for setting up sirius from the Emerging Stack dockerfile (end-to-end) ####NOTE: Everything here works on a laptop, but it will run out of disk space in all likelihood, requiring an annoying boot2docker hack. It's easier and faster in the cloud. You can copy/paste each of the commands below...without the dollar or hash symbol. Remember, if you terminate your DigitalOcean droplet, you'll have to do all these steps again (but they will survive a server reboot).

####At the end of this process, you will be able to ask Sirius some wikipedia type questions (when, which, where, etc) inside a terminal window...don't expect a fancy user experience, this is raw functionality only.

###Cloud Server Provisioning Stage

1. Sign in to digitalocean and set up an account, billing, etc

2. Setup new droplet ($40 month size with Ubuntu 14.04)...wait 1 minute