Month: March 2016

State of the Layer: All Hands – March 29 2016

Adam
  • Craig
    1. Lots of progress on integrations and protocol enhancements
    2. Working with NTU students for currency issuance proposals
    3. UIT testing will begin in the next couple of weeks
    4. OmniCore DEX Phase I support?
    5. OmniWallet release?
  • Adam
    1. Omniwallet
      1. Ongoing: managing support
      2. Final Reviewing/testing staging branch with Tomas
        1. Merged to rebrand branch.
  • Patrick
    1. Huge progress on logic and testing arb system, wait til you see my Trello
    2. Drafted brief for explainer video
    3. Good week for capital, done selling OMNI for the foreseeable future, played that BTC flip it and reverse it decently.
  • Marv
    1. Omni spec
      1. PR for OmniDex 2.0 needs review https://github.com/OmniLayer/spec/pull/316
      2. Need Class C transaction description
      3. Other known changes in latest release
        1. Feature activation
        2. …?
      4. Intend to re-organize and clean it up
    2. Omniwallet
      1. Watching for support tickets
  • Sean
    1. OmniClientJS
      1. Added RegTest support and can now drive OmniCore in RegTest mode
    2. OmniJ
      1. Update to latest bitcoinj (notably) fee changes
      2. Minor bug fixes
    3. OmniPortfolio
      1. Dynamic Pie Charts for currency distribution by address (in progress)
  • Zathras
    1. OmniChest
      1. Support requests for API increasing, starting to finalize ‘ask’ API & documentation so it can get published
      2. Working on adding a new database model with better indexing to speed up response times for API

State of the Layer: All Hands – March 22 2016

State of the Layer: All Hands – March 29 2016

State of the Layer: All Hands – March 22 2016

Adam
  • Adam
    1. Omniwallet
      1. Ongoing: managing support
      2. Patch for armory offline signing
      3. Reviewing/testing staging branch with Tomas
    2. OmniDex Getting Started Guide
  • Patrick
    1. CNY Trading testing for consistent profitable order placement
    2. Made a lot of progress with Zathras re: Subscribe to Smart Contract tx and associated Publish Hash/Publish Secret
    3. Good week for capital – OMNI up 40% on rising volume
    4. Reviewed OmniClientJS with Sean for use in feature testing and Dex trading
  • Marv
    1. Omniwallet
      1. User support as needed
    2. Omni spec
      1. Adding OmniDex 2.0 transaction types, and related cleanup
        1. Leave liquidity bonus in? No, Dexx recommends removing whatever’s not implemented.
  • Sean
    1. OmniClientJS
      1. Had productive code walkthrough/review with Patrick
      2. Converting JavaScript omniXxx methods to “static” methods so they can be documented with JSDoc and be self-documenting and auto-completing in IDEs.
      3. Embracing EcmaScript 2015 — because we’re requiring Node.js 4.x LTS. Arrow functions FTW!
      4. Continuing to use the Bitcoin JSON-RPC client NPM named bitcoin (by “freewil”), but looking at alternatives, not intending to maintain long-term compatibility with that lower-layer.
  • Zathras
    1. OmniCore:
      1. Further work on MetaDEx fees concept
      2. Improved testing scripts
      3. Fixed a number of bugs picked up with testing
      4. Added persistent storage for fee distribution history
      5. Added recording of recipient/amount data during fee distribution
      6. Added RPC calls:
        1. omni_getfeedistribution – retrieve a fee distribution (incl recipients) by distribution id
        2. omni_getfeedistributions – retrieve all past fee distributions (incl recipients) for a property id
    2. OmniChest:
      1. Further work on adding support for UT
      2. Working on version patch to address some feedback
      3. Support (API requests etc)
  • Dexx
    1. Slowly getting back on my feet and still catching up.
  • Judith
    1. On going projects
    2. New projects
    3. Reaching out to crowdsale platforms (coordinated with Patrick)
    4. Posting around + arranging meeting

State of the Layer: All Hands – March 15 2016

State of the Layer: All Hands – March 22 2016

OmniDex: Getting Started

Adam

With the recent announcement of Omni’s Distributed Meta Token Exchange (OmniDex v2) we have noticed an increase in requests for a ‘Getting Started’ guide.  So without further ado we present: OmniDex v2, Getting Started Step-by-Step. Note: v2 of the OmniDex adds support for trading Omni smart property tokens for Omni tokens.

Requirements and Software:

  • At the moment the new OmniDex is only available in the Omnicore client, so if you haven’t yet downloaded/installed it head over to the download page (http://www.omnilayer.org/download.html) and grab your copy.
    • Note: Omnicore is a drop in replacement for BitcoinCore. So if you already have BitcoinCore downloaded/installed then once you install Omnicore you should make sure BitcoinCore is stopped before starting OmniCore.
  • If you have any special startup commands/flags for BitcoinCore, configure your Omnicore startup link/script with the same commands/flags.

Launching and Syncing the client

  1.   Upon first launch of the client you’ll see several loading messages as the client starts to parse the existing data and startuploading.pngverifying.pngloading wallet.png
  2. Once completed you’ll be greeted with the main client window.  The current blockchain state/network status will be displayed in the bottom bar.Main Page.png
  3. Wait for your client to sync to the blockchain. Once it is up to date and current you can move on to checking/importing your addresses.
    1. If you’ve never run BitcoinCore or OmniCore before the initial sync/download of the blockchain will take approx 50-70Gb of hardrive space and several hours – days to complete the initial sync

 

Checking/Importing your addresses

  1.  Once your client is synced,  if you had a BitcoinCore wallet on your system you will see your balances displayed. You can also check the addresses the wallet knows about by going to ‘File -> Receiving Addresses’ addresses.png
  2. If you did not have a BitcoinCore wallet already you will need to either import the addresses that contains your Omni Tokens/BTC  or alternatively you can send Omni Tokens/BTC to the address displayed in your wallet.

    • Sending Funds to your wallet

      1. If your Omni tokens and BTC are on a different address that you do not want to import you can simply send them to one of the addresses listed in your wallet above

    • Importing an Address

      1. To import an address into OmniCore go to the ‘Help -> Debug’ menu and then click on ‘Console’ console.png
      2. Next you’re going to need the private key for the address you want to import. Once you have the private key run the following command:
        importprivkey “bitcoinprivkey” “optional label”

        • Note: If you are planning to import more than 1 address run the command as:   importprivkey “bitcoinprivkey” “optional label”  false  for each address you want to import except the last one. For the last one run the original command above (without the false)
        • If importing multiple addresses the label can be a pair of empty quotes “” if you do not wish to label the addresses.
      3. Once you start the importprivkey command,  walk away. Go get a drink, go change the laundry, unpack the dishwasher even. Whatever it is just go do something else.
      4. I’m not kidding. The import process will take a good 5-30 minutes as it rescans the entire blockchain data on your computer looking for information about the address.  During this time it will look like it’s frozen. It’s not, just let it do it’s thing.
      5. Once the address import finishes you should get a response from the console indicating the import result/status. If it went well you should be good to go and actually start trading.

Your first trade on the OmniDex

  1. Now that everything is up and running and you are ready to make a trade let’s head over to the ‘Exchange’ tab on OmniCore and check it out.Exchange.png
  2. The first page you’ll come to will be the Exchange page for MaidSafeCoin (Prop ID 3)
    • You’ll notice in this example that right now there is 1 buy offer to purchase 100 Maid’s for 2.5 Omni’s
  3. If you wish to trade / view a different currency simply enter the currency ID in the top right corner and click ‘Switch’.  Popular currencies and their propertyid include:
    • Maidsafe – 3
    • TetherUSD – 31
    • Agoras Tokens – 35
    • Synereo AMP – 39
    • SafeExchangeCoin – 56
    • SAFE App Store Coin – 57
    • For more info about a property id you can use
  4. To trade, simply select the address you wish to use and either click an existing open trade to automatically populate the amount & price fields or enter your chosen values manually. Finally click the Buy or Sell buttons accordingly.
  5. Your trade will be broadcast to the network. Once your transaction confirms it will either match an existing order and immediately credit your account the matched amount or it will sit on the network waiting for a match. (Any unmatched portion of your trade will wait for a match until it is filled or canceled by you)
    1. You can check your trade history to see any matches/existing trade information on the ‘Trade History’ tab under the Exchange menu

Cancelling Existing Orders

  1. You can cancel any existing trades still on the market by going to the ‘Cancel Order’ tab of the Exchange menu and selecting the address for which you have open orders you want to cancel. Each cancel transaction will affect only the orders from the address you have chosen and your cancel options are:
    • Cancel by Pair: Cancels all orders that match the Buying/Selling Pair
    • Cancel by Price: Cancels all order that match the specific price
    • Cancel by Ecosystem: Cancels all orders in the Production or Test ecosystem.
OmniDex: Getting Started

State of the Layer: All Hands – March 15 2016

Adam
  • Craig
    1. Been travelling all over the place, speaking about Omni, Tether, and digital objects
      1. Amsterdam: d10e conference
      2. Zurich: digital objects
      3. Taiwan: spoke at the National Taiwan University and Taiwan Academy of Banking and Finance
        1. Will be working with professor on adding Omni to the blockchain curriculum at the most prestigious university in Taiwan!
    2. Interesting discussions around ethereum scripting
      1. What would it take to snag the pyethereum code and try some small contracts on testnet?
      2. We have some serious third-party interest in doing this to increase Bitcoin capabilities without a fork discussion
    3. Nested smart properties….?
      1. Looking to integrate “folders” within the protocol
      2. Each asset could use a “parent-id” field to designate the “folder” property that “contains” it
        1. Either pre-existing assets could be used for this purpose, or a generic “folder creation” transaction could create a meta-asset with an id that could be used to contain other assets
      3. A single transaction of a smart property/folder would move the asset as well as any asset in the same address with the first asset’s id.
    4. Many more ideas coming … will be back home next week and will update the team.  Looking forward to giving everyone some exciting updates!
  • Adam
    1. Omniwallet
      1. Ongoing: managing support
      2. Reviewing/testing staging branch with Tomas
  • Patrick
    1. Figured out how to issue blockchain securities/REITs legally and be able to market/sell to non accredited US persons in 28 states
    2. Designed futures trading model that ought to generate ~10k in monthly income, moving to implement
    3. Finished traveling for a while
    4. Started UI wireframes
    5. More progress on smart contract tx
  • Marv
    1. Omniwallet –
      1. Testing staging release candidate, finding & reporting items to Adam
      2. Handling support requests
  • Sean
    1. Website update later this week.
    2. Looking into test framework for OmniClientJS
    3. Thinking ab out Omni fee model (will open Github issue)
    4. Attended Andrey Zamovskiy’s talk “Growing a Cryptocurrency Beyond Early Adopters”  in SF.
  • Zathras
    1. OmniCore
      1. Further work on fees
        1. Floating threshold based on x% of total tokens
        2. Reorg proofing and testing
        3. Need to clarify requirements on past fee distribution data availability on RPC layer
      2. Wrote PR for transaction removal from mempool for Adam (https://github.com/OmniLayer/omnicore/pull/353) – TBD
    2. OmniChest
      1. Started work on adding support for UT to OmniChest
      2. Base schema work to support ranges ongoing
  • Tomas
    1. Omniwallet
      1. Went through the issues reported in the PR for the rebrand
      2. Lots of fixes done
      3. Working with Adam to get to merging point
      4. Will get any major bugs on the PR fixed and we can move with the rest later.
  • Judith
    1. On going projects
    2. New projects
    3. Reaching out to crowdsale platforms (coordinated with Patrick)

State of the Layer: All Hands – March 08 2016

State of the Layer: All Hands – March 15 2016

State of the Layer: All Hands – March 08 2016

Adam
  • Craig
    1. Been travelling all over the place, speaking about Omni, Tether, and digital objects
      1. Amsterdam: d10e conference
      2. Zurich: digital objects
      3. Taiwan: spoke at the National Taiwan University and Taiwan Academy of Banking and Finance
        1. Will be working with professor on adding Omni to the blockchain curriculum at the most prestigious university in Taiwan!
    2. Interesting discussions around ethereum scripting
      1. What would it take to snag the pyethereum code and try some small contracts on testnet?
      2. We have some serious third-party interest in doing this to increase Bitcoin capabilities without a fork discussion
    3. Nested smart properties….?
      1. Looking to integrate “folders” within the protocol
      2. Each asset could use a “parent-id” field to designate the “folder” property that “contains” it
        1. Either pre-existing assets could be used for this purpose, or a generic “folder creation” transaction could create a meta-asset with an id that could be used to contain other assets
      3. A single transaction of a smart property/folder would move the asset as well as any asset in the same address with the first asset’s id.
    4. Many more ideas coming … will be back home next week and will update the team.  Looking forward to giving everyone some exciting updates!
  • Adam
    1. Omniwallet
      1. Ongoing: managing support
      2. Reviewing/testing staging branch with Tomas
      3. Patched error introduced by Chrome update from past week
  • Patrick
    1. Adventures in intl. structuring
    2. Discussed partnership with dev company to pipeline sponsored apps
    3. Yield is >.3% a day, thank you Ethereum bubble
  • Marv
    1. Omniwallet –
      1. testing release candidate, reporting items to Adam
      2. Following support requests
    2. Tether
      1. Got upgraded to multi-sig address for my account
  • Sean
    1. OmniClientJS
      1. Github repository renamed from OmniTradeJS
      2. OmniClient is now a class and initialized with new operator
      3. All methods from earlier implementation are available and support Promises.
      4. Waiting for feedback from Patrick and any other interested developers.
    2. www.omnilayer.org
      1. Finishing download page later today
      2. Adding page with currency issuance guidelines.
  • Zathras
    1. Few support requests for API help dealt with
    2. Assisted @dexx with consensus hashing debugging for his 0.12 work
    3. Prototype of fees working(ish) – fees are stripped from the liquidity taker and moved into a cache which maintains a 50 block history (for cases of reorgs).  When distribution threshold reached fees are distributed via existing STO logic.  Next stage will be developing adaptive distribution threshold (currently fixed for testing).
    4. http://omnichest.info/testnet/feetests.txt
  • dexx
    1. Further help with exchange integration
    2. Making good progress with port of Omni Core to 0.12 code base
  • Judith
    1. On going projects
    2. New projects
    3. Reaching out to crowdsale platforms (coordinated with Patrick)

State of the Layer: All Hands – March 01 2016

State of the Layer: All Hands – March 08 2016

State of the Layer: All Hands – March 01 2016

Adam
  • Adam
    1. Omniwallet
      1. Ongoing: managing support
      2. Reviewing staging branch with Tomas
    2. OmniEngine
      1. updated for dex 2.0
        1. We’re live
  • Patrick
    1. Massive biz dev, first crypto-REIT is in the works
    2. Interop/Smart Contract subscribe spec, met with Credits team, continuing to hammer down on it
    3. Getting about .2% a day between Po
    4. Answering PR questions for interviews
  • Marv
    1. Omniwallet – watching the support issues
    2. Subscribe tx – just read issues 345, 346, 347; need clarification
  • Sean
    1. OmniClientJS (formerly OmniTradeJS)
      1. Now an EcmaScript subclass of  Bitcoin RPC client
      2. Demo of JavaScript promises for cleaner async support
      3. Need to rename repository for new name
      4. Hope to finish conversion today
    2. Website update (download page with instructions) coming soon
  • Zathras
    1. OmniChest
      1. Additional APIs deployed as per request
      2. Work for new API solution ongoing
    2. OmniCore
      1. Submitted PR with a couple options for storing a transaction position in block for RPC
  • dexx
    1. Porting Omni Core to 0.12 code base
  • Judith
    1.  Reaching out real estate companies/projects
      1. Ongoing projects
      2. New projects
      3. Reaching out to crowdsale platforms (coordinated with Patrick)

State of the Layer: All Hands – Feb 23 2016

State of the Layer: All Hands – March 01 2016