State of the Layer: All Hands – June 20 2017

  • Craig
    1. Tether will be issuing USDT on Omni on Litecoin 😀
      1. Details will be forthcoming
      2. Will allow users to convert
      3. Exchanges ready to support
    2. Deloitte follow-up
      1. Looking to leverage the use cases provided
      2. Will be providing them additional detail on:
        1. auditing,
        2. crowdsale automation and
        3. decentralized identity
    3. RSK (Rootstock) Node setup
      1. Omni Foundation will be a validating node in the RSK Federation
      2. Will help validate USDT issuances on Bitcoin and RSK chain
      3. Still needs the secure channel setup and node deployed
    4. Omni Core 0.2 release updates
      1. BTC crowdsales?
    5. vAtomic vAtoms / Digital Objects proof of concept
      1. Got the go-ahead to proceed
      2. Dedicated Omniwallet instance, prior to ICO
      3. Will be using Uniquely Identifiable Tokens (UIT) build on TestNet
      4. Will be overlaying viewer.vatomic.io code onto Omniwallet
      5. Showing movement of objects on-chain and off-chain (and in between)
  • Zathras
    1. OmniExplorer:
      1. Swapped in new/rebuilt instance of OE (thanks @adam)
      2. New getblocktx API live, now precached when block is mined so no longer requires heavy database access at request time
      3. Added basic support for warning users when a transaction uses a property with a duplicate/similar name to an existing property
    2. Omni Core:
      1. Generated & tested checkpoint hash for block 470,000 on both 0.0.12 & 0.2 (https://github.com/OmniLayer/omnicore/pull/480)
      2. Generated & tested seed blocks for blocks 460,000 to 470,000 on both 0.0.12 & 0.2 (https://github.com/OmniLayer/omnicore/pull/481)
      3. Efforts to diagnose hash mismatches when deterministically building 0.2 via Gitian, builds are the same but 3 sets of bytes (29 bytes total) are causing hash mismatches
  • dexx
    1. Building binaries for Omni Core 0.2
    2. Website overhaul
  • Adam
    1. Omniwallet
      1. Handling support
      2. Pushed updates to handle changes to 3rd party api’s
      3. Looking into multisig/hardware wallets support
      4. Looking at manage issuance/management
    2. Omnicore
      1. Upgraded omniwallets backend to Omnicore 0.2
      2. Identified some additional upgrade notices that were needed for integrators
  • Sean
    1. OmniDroid (Omniwallet/OmniPortfolio for Android)
      1. It lives! (Adam check your server logs)
    2. OmniPortfolio
      1. Release waiting on Omniwallet multiaddr balance upgrade
    3. OmniJ
      1. 0.5.2 coming this week

State of the Layer: All Hands – June 13 2017

State of the Layer: All Hands – June 20 2017

State of the Layer: All Hands – June 13 2017

  • Craig
    1. D10e Conference in Tel Aviv was a success!
      1. Great reception on Omni advancements
      2. Digital Objects were extremely well received
      3. Decentralized Identity requests coming in
      4. Potential arrangement with the EOS team for interoperability
    2. Deloitte meeting in Israel
      1. Discussion around actionable blockchain projects for their clients
      2. Proposal submitted for managed asset tracking and identity projects
        1. Has been sent to HQ
    3. RSK (Rootstock) Node setup
      1. Almost complete
      2. Will be a validating node in the RSK Federation
      3. Will help validate USDT issuances on Bitcoin and RSK chain
    4. Omni Core 0.2 release updates
      1. UI vs RPC?
    5. vAtomic vAtoms / Digital Objects proof of concept
      1. Dedicated Omniwallet instance, prior to ICO
      2. Will be using Uniquely Identifiable Tokens (UIT) build on TestNet
      3. Will be overlaying viewer.vatomic.io code onto Omniwallet
      4. Showing movement of objects on-chain and off-chain (and in between)
  • Zathras
    1. OmniExplorer:
      1. Reconstructed everything from backups following security incident (firewall restrictions dropped for approx 4-6 hours).  Appears regular (non-firewall) security measures did their job & no compromises detected following review but for safety & 100% confidence all components have been restored from clean backups, preparing to swap out production with replacement.
      2. Fixed (partially) support for missing Send All transactions, working on fixing full support for subsends
    2. OmniCore:
      1. Reindexed blockchain for OC 0.0.12 and compared various consensus hashes with OC 0.2 to further verify release
      2. Diagnosed & resolved Gitian build failure for 0.2 release due to version format (https://github.com/OmniLayer/omnicore/pull/479)
      3. Generated & signed Gitian builds for 0.2 release
  • dexx
    1. FInalized release notes for Omni Core 0.2:
      https://github.com/OmniLayer/omnicore/pull/461
    2. Merged develop branch into master branch, finalizing Omni Core 0.2:
      https://github.com/OmniLayer/omnicore/pull/477
    3. Tagged Omni Core 0.2 release on GitHub:
      https://github.com/OmniLayer/omnicore/releases/tag/v0.2.0
    4. Built deterministic binaries for Omni Core 0.2 and released Gitian results:
      https://github.com/OmniLayer/gitian.sigs/pull/41
    5. Up for discussion:
      1. Pin Reddit contact information of developers on /r/omni
      2. Publish GPG keys of developers on Reddit/…
  • Adam
    1. Omniwallet
      1. Handling support
      2. Issue over weekend required some restarts to clear up service locks
      3. Looking into multisig/hardware wallets support
      4. Looking at manage issuance/management
  • Sean
    1. Ongoing improvements in OmniPortfolio/OmniJ/bitcoinj-addons
    2. Waiting for Omniwallet fixes for pending OmniPortfolio release
    3. Consensus tests may have found an OmniExplorer glitch
    4. Studying a handful of other Crypto and ICO projects for various reasons
  • Patrick
    1. Exploring JV for OmniLite development

State of the Layer: All Hands – June 06 2017

State of the Layer: All Hands – June 13 2017

State of the Layer: All Hands – June 06 2017

  • Craig
    1. Conference D10e
  • Zathras
    1. Omni Explorer:
      1. Refreshed infrastructure to handle further increasing loads
      2. Rewrote API ban code & request tracking to allow better filtering (protection measure, improve availability)
    2. Omni Core:
      1. Various discussions & planning for 0.2 release
      2. Reviewed and wrote tests for dust exclusion PR from dexx
      3. Reviewed and tested input cache locking PR from dexx
      4. Started working on improving Class D prototype to include virtual references
  • Adam
    1. Omniwallet
      1. Handling support
      2. New Wiki pages
      3. Updated dynamic fee for OmniDex 1.0 cancels
      4. Looking into multisig/hardware wallets support
      5. Looking at manage issuance/management
  • Sean
    1. OmniPortfolio 0.1.2 waiting for Omniwallet fixes
      1. Release of multi-address balance query to production
      2. Fix for address-balance rate limit #1507
    2. Continued OmniPortfolio development against staging server
      1. Support for Kraken USDT/USD exchange rate
      2. Reduced server load *and* increased performance
      3. Reduced application thread count
    3. OmniJ and bitcoinj-addons improvements, as well.
  • Marv
    1. Omniwallet
      1. Wiki pages w/ Adam

State of the Layer: All Hands – May 30 2017

State of the Layer: All Hands – June 06 2017

State of the Layer: All Hands – May 30 2017

  1. Craig
    1. Traveling
  2. Zathras
    1. Omni Explorer:
      1. Fixed a bug with reorg protection that allowed a transaction to be entered twice in the database if the reorg occurred while the engine was not in sleep mode (eg while it was actively parsing)
      2. Updated the engine to improve handling of pending transactions (a new cache for transactions that are not yet in a block avoids burning compute resources by repeatedly reprocessing pending transactions over and over)
      3. Updated the engine to add additional locks & an extra temp table to hold processed blocks (avoids race condition that in rare circumstances may allow the API to return an apparently empty block when there are in fact Omni transactions in it)
    2. Omni Core:
      1. Fixed a number of bugs in the QT UI for v0.2 (https://github.com/OmniLayer/omnicore/pull/471)
      2. Reviewed dexx’s PR for hardcoding activation heights (https://github.com/OmniLayer/omnicore/pull/470)
  3. Dexx
    1. Reviewed Class D pull request:
      https://github.com/OmniLayer/omnicore/pull/469
    2. Reviewed final pieces for the Qt UI:
      https://github.com/OmniLayer/omnicore/pull/471
    3. Hardcoded activations up to block 438500:
      https://github.com/OmniLayer/omnicore/pull/470
    4. Locked fetching and processing inputs while parsing:
      https://github.com/OmniLayer/omnicore/pull/472
    5. Removed sigops workaround for wallet transactions:
      https://github.com/OmniLayer/omnicore/pull/473
    6. Finalized Omni Core 0.2 release notes:
      https://github.com/OmniLayer/omnicore/pull/461
    7. Created tutorial for creating raw Omni sends:
      https://gist.github.com/dexX7/352670c990ebf9ea31d6346a1519eb52
  4. Adam
    1. Omniwallet
      1. Handling support
      2. Looking into multisig/hardware wallets support
      3. Looking at manage issuance/management
  5. Sean
    1. Bitcoinj-addons
      1. v0.2.3 released (CHANGELOG)
      2. Started work on v0.2.4-SNAPSHOT
    2. OmniJ
      1. v0.5.1 released (CHANGELOG)
      2. Started work on v0.5.2-SNAPSHOT
    3. OmniPortfolio
      1. 0.1.2-rc-1 released (privately, on Slack)
      2. Waiting for Omniwallet Bitcoin balance fetching improvements for 0.1.2 final release
      3. Ongoing improvements

State of the Layer: All Hands – May 23 2017

State of the Layer: All Hands – May 30 2017

State of the Layer: All Hands – May 23 2017

  1. Craig
    1. Consensus Conference
  2. Zathras
    1. Omni Explorer:
      1. Added unique tokens capabilities to a new development instance tracking UIT only
      2. Performance issues, substantial increases in usage, working on upgrades and optimizations
      3. Continuing work on Omni Explorer v8
    2. Omni Core:
      1. Minor improvements to next feature prototypes
  3. Adam
    1. Omniwallet
      1. Handling support
      2. Added new v2 address query for sean
      3. Looking into multisig/hardware wallets support
      4. Looking at manage issuance/management
  4. Sean
    1. Bitcoinj-addons v0.2.3 released
    2. OmniJ v0.5.1 ready for release
    3. OmniPortfolio v0.1.2 will be released when “multi-address balance query” goes live on Omniwallet
  5. Marv
    1. Omniwallet
      1. User support

State of the Layer: All Hands – May 16 2017

State of the Layer: All Hands – May 23 2017

State of the Layer: All Hands – May 16 2017

  • Craig
    1. Tether arbs with taiwan customers has restored the price back to the peg
    2. Travel
      1. Will be in NY next week for Consensus / TokenSummit
      2. Will be in Israel the following two weeks for d10e, meeting with potential sponsors & partners
    3. Omni Core 0.2 status?
    4. Deloitte proposal?
    5. Protocol enhancement usage
      1. Uniquely Identifiable Tokens
        1. Getting a build of Omniwallet that supports digital objects
        2. Will be testing the prototype with specific use cases
      2. Core.ID / meta-data / address tagging
        1. Will be working with coretech devs on protocol integration
    6. Omnilayer.org redesign and content
      1. Will be engaging a designer
      2. We need to prep how-to’s, walkthroughs and descriptions
    7. Litecoin private release
      1. Emails to alpha@omni.foundation has provided some feedback
    8. Integrators
      1. Made inquires about 0.0.12 update status
      2. Still need feedback from other large integrators
        1. Who else do we need?
  • Zathras
    1. Omni Explorer:
      1. Further patched Omni Engine to tolerate pending bug with unreleased 0.2.  Confirmed success (26 occurrences of bug, zero failures)
      2. Rewrote Omni Engine’s supporting library (DLL) to have a much larger debugging footprint in an effort to get more granular troubleshooting data
      3. Started work on Omni Explorer v8 (based on various user feedback over the last year & with a focus on multiple blockchain support)
    2. Omni Core:
      1. Updated Class D pull request based on feedback (thanks to @dexx7)
      2. Continuing the ongoing work on next features to support integrators (class D, central fees, sendmany etc)
  • Adam
    1. Omniwallet
      1. Handling support
      2. Worked with marv to improve db queries and speed up wallet load time
      3. Looking into multisig/hardware wallets support
      4. Looking at manage issuance/management
  • Sean
    1. bitcoinj-addons v0.2.3 due later this week
      1. Dependency updates only (some are important)
    2. OmniJ v0.5.1 due later this week
      1. Dependency updates
      2. Bug fixes and ecosystem compatibility updates
      3. Omniwallet REST client improvements (for OmniPortfolio, etc)
    3. OmniPortfolio v0.1.2 due next week
      1. Dependency updates
      2. Omniwallet balance query performance improvement
  • Patrick
    1. Assessing a new opportunity that would bring resources to the platform

State of the Layer: All Hands – May 09 2017

State of the Layer: All Hands – May 16 2017

State of the Layer: All Hands – May 09 2017

  • Zathras
    1. Omni Explorer:
      1. Recovered several brief outages caused by pending bug in Omni Core 0.1.99, getting more frequent as more transactions are pending
      2. Omni Engine has been patched to attempt to tolerate recurrences of above bug, in testing now
    2. Omni Core:
      1. Attempting to diagnose 500 error from RPC server when querying pending transactions (roughly one occurrence per 50,000 requests)
      2. Submitted minor PR for a fix on change issuer RPC (https://github.com/OmniLayer/omnicore/pull/468)
      3. Submitted PR for prototype of a new transaction class (D) with compressed payloads (https://github.com/OmniLayer/omnicore/pull/469)
      4. Continuing to work on next features to support integrators (class D, central fees, sendmany etc)
  • Adam
    1. Omniwallet
      1. Handling support
      2. Pushed additional websocket patches for balance data and improvements
      3. Looking into multisig/hardware wallets support
      4. Looking at manage issuance/management
  • Patrick
    1. Expanded Deloitte Proposal – focusing on identity verifiers, contingent tx oracle roles, use cases that can be prototyped as app-level functionalities using RPC
    2. Airbitz Integration
    3. Sphere Crowdsale

State of the Layer: All Hands – May 02 2017

State of the Layer: All Hands – May 09 2017