State of the Layer: All Hands – Dec 19 2017

  1. Craig
    1. With 0.3 release complete need to start circling back up on Digital Objects (UIT/vAtomic )
  2. Adam
    1. Omniwallet
      1. Handling support
    2. Omnicore
      1. Helping with integrators as needed
    3. Planning for 2018 updates for Omni
      1. Increase social presence
      2. Brand awareness
      3. Looking for additional devs
  3. dexx
    1. During the last days, I prepared the 0.3 release with Z, uploaded the binaries, updated the website, sent out the announcements etc. Then I started with some rather large refactor of Omni Core to make it easier to get an understanding which parts are where.
    2. Working on the new website release
      1. Update released Dec 20

State of the Layer: All Hands – Dec 12 2017

State of the Layer: All Hands – Dec 19 2017

Omni Core v0.3 Released

We are pleased to announce the release of Omni Core v0.3

v0.3.0 is a major release and consensus critical in terms of the Omni Layer protocol rules. This release supersedes and replaces all previous releases, an upgrade is mandatory as prior releases will not be compatible with new behaviour in this release.

A few key things about this upgrade:

  • To avoid any possible database corruptions/needing to rebuild the blockchain db any running client will need to perform a clean stop using the rpc command “omnicore-cli stop”
  • Upon launching the new update your client will need to reparse the current Omni Layer transactions. Depending on the speed/power of your machine this may take 30-90 minutes so please plan accordingly.

Please see the full release notes here for additional information as well as install/upgrade instructions.

Download links can be found either on github or bintray 

Omni Core v0.3 Released

State of the Layer: All Hands – Dec 12 2017

  • Craig
    1. Traveling
  • Adam
    1. Omniwallet
      1. Handling support
    2. Omnicore
      1. Helping integrators 
  • Zathras
    1. Omni Explorer
      1. Significant load spikes related to high volumes of Omni tx’s, throwing more resources at OE in short term
      2. Optimizing caching and improving ban code for API abuse
    2. Omni Core
      1. Development of Freeze system
      2. Working towards Omni Core 0.3
  • dexx
    1. Reviewed, tested and merged reintroduction of client shutdown and freeze transactions
    2. Finalized, built and uploaded Omni Core v0.3
    3. Still waiting for more review of website overhaul (https://github.com/OmniLayer/omnilayer.github.io/pull/19)
  • Marv
    1. Omniwallet
      1. support

State of the Layer: All Hands – Dec 5 2017

State of the Layer: All Hands – Dec 12 2017

State of the Layer: All Hands – Dec 05 2017

  • Craig
    1. Tether and Omni Layer relationship clarification
      1. Omni Layer is an open-source project, unrelated to any corporation
      2. Tether is simply the largest issuer of assets on the Omni Layer
        1. Among many other issuers like MaidSafe, Synereo AMPs, and Tau Chain Agoras.
    2. Digital Objects
      1. Want to release the new Omniwallet with digital object / vAtom code asap
      2. Zathras, can you help with a tutorial with Andrew?
      3. Next steps:
        1. Testnet example of omniwallet, hosted by vAtomic
          1. Make sure this works as expected
        2. Merge that testnet code for OW into mainnet OW (even though Core doesn’t yet support UIT)
        3. Publish tutorials for creating digital objects for non-UIT tokens
        4. Complete the UIT buiild for mainnet test scosystem
          1. Testing, activation, etc.
        5. Deploy UIT version of Core
        6. Update tutorials for unique tokens
    3. Recovery status
      1. New build with Freeze function
  • Adam
    1. Omniwallet
      1. Handling support
  • Zathras
    1. Omni Core
      1. Continuing to work on building new freezing feature
    2. Omni Explorer
      1. Recovered outage caused by overusage of a specific API call
      2. Working to optimize API queries that use large amounts of resources

State of the Layer: All Hands – Nov 28 2017

State of the Layer: All Hands – Dec 05 2017

State of the Layer: All Hands – Nov 28 2017

  • Craig
    1. Recovery discussions
      1. A reclaim really is “stealing” coins back
      2. No integrator has accounted for these kinds of changes in balances after a transaction
      3. Instead, we want to “retire” tokens in an address, so that they can stay frozen
        1. With an option for “unfreeze” – where issuer could unfreeze with required destination (maybe issuer address?)
        2. “Frozen” tokens won’t be included in the total coins in circulation number
      4. Enabling freezing for an issuer will have a one-month notice period
  • Adam
    1. Omniwallet
      1. Handling support
  • Zathras
    1. Working on Omnicore
  • Marv
    1. Omniwallet
      1. User support
    2. Will write up a protocol-independent mechanism to enable senders to ensure they are sending to an address that is able to use the tokens that are sent

State of the Layer: All Hands – Nov 21 2017

State of the Layer: All Hands – Nov 28 2017

State of the Layer: All Hands – Nov 21 2017

  • Craig
    1. Don’t bother stealing tethers
      1. Amazing job by the Omni team to assist Tether in retrieval / ring fencing
        1. Congrats guys
      2. Tether released a blacklist version of Omni Core for exchanges to block the hacker
        1. Temporary measure until the new Omni Core comes out shortly
        2. Omni Foundation will *not* merge any blacklists into the official release
          1. This is fundamentally against our ethos
      3. New builds with feature activations already broadcast to allow Tether to reclaim the tokens
        1. This will also work for stuck tokens at Coinbase, etc (lost tokens that are stuck at incompatible exchanges)
      4. Hard fork will be rectified with the new Omni Core version
        1. Like the hack never happened
    2. Omni proves itself as the most flexible foundational asset technology for token issuers 🙂
      1. Omni provides a variety of features for issuers, they get to choose which ones they want
      2. Managed asset issuers will now have the ability to reclaim tokens – which some users may not like
        1. So I’ll make sure Tether announces this capability prior to the new build going live so users have the option of exiting the Tether ecosystem if they are philosophically opposed to this capability
    3. I am so proud of this team – this is the best team in all of crypto.  Well done, folks.
      1. People are beginning to realize how profound the tech is that we’ve built on top of Bitcoin
  • Adam
    1. Omniwallet
      1. Backend daemon crashed. Reparsing/rebuilding blockchain now/
        1. Going to take a while 😦
      2. Handling support
    2. Assisting with Tether
  • Zathras
    1. New Omni Core Pull Requests
      1. this one is cool – https://github.com/OmniLayer/omnicore/pull/508 – updates the consensus hashing system to enable balance hashing only
      2. this one is super cool – https://github.com/OmniLayer/omnicore/pull/507 – includes the reason for a transaction being invalid in the RPC response :slightly_smiling_face:
      3. this one is just a basic bugfix – https://github.com/OmniLayer/omnicore/pull/505 – cleans up log spam
  • Sean
    1. bitcoinj-addons project (Bitcoin base layer for OmniJ) is moved/renamed to ConsensusJ
    2. Rivetz work
  • Marv
    1. Omniwallet
      1. User support

State of the Layer: All Hands – Nov 14 2017

State of the Layer: All Hands – Nov 21 2017

State of the Layer: All Hands – Nov 14 2017

  • Adam
    1. Omniwallet
      1. Back and catching up/Handling support
  • Zathras
    1. Omni Explorer:
      1. Recovered several outages due to load spikes burning through allowed resources, ready & keen to go live with new infra
      2. Working on a fix for a set of circumstances that could cause the API to report there were no transactions in a block, when in fact there were
    2. Omni Core:
      1. Fixed spam log entries from unconfirmed transactions (https://github.com/OmniLayer/omnicore/pull/505)
      2. Working on an update to Omni Core that will persistently store the reason for a transaction being invalid and enable query via RPC (instead of requiring log review)
      3. Revisiting send-many, believe I have a technically viable solution to send-many that supports up to 10x recipients within 80 byte nulldata
    3. General:
      1. Support tickets
  • Sean
    1. Online discussion of Omni “safe address” proposals with Marv, Zathras, Dexx
    2. Rivetz work
  • Patrick
    1. Speaking on behalf of Ale/Lihk, xTrade re-write and priceMap changes in effect. Going to ship a basic logic test for these values soon.
    2. Following up with build for establishing createContract on testnet and RPC for returning info on contract

State of the Layer: All Hands – Nov 7 2017

State of the Layer: All Hands – Nov 14 2017