• 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

• 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

• 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

• Patrick
  1. Flow diagram’ed for settlement algo, researching graph theory for last function, have defined:
     1. settlementFlowLoop
     2. getLiveContracts function
     3. Index of nettings produced as bi-product of getLiveContracts function
     4. Last piece of the puzzle is graph function to find net-zero shortest paths for final settlement
  2. Waterfall flow established for logic prototypes -> C++ code -> test suite -> live testing->optimization -> more testing->maybe launch
• Zathras
  1. Omni Explorer:
     1. Fixed a server error with statistics, patch from dev going into prod today
     2. Fixed a couple minor issues with the new infra, reading and waiting to go
  2. Omni Core:
     1. Added PR to make consensus hashes ecosystem specific (https://github.com/OmniLayer/omnicore/pull/502)
     2. Working on minor tweaks to UIT
     3. Working on minor updates for performance optimization
  3. General:
     1. Support
• Ale/Lihk
  1. Building new important classes  (.h and .cpp files) to define the main functions for ContractDex.
  2. Figuring out data model. (priceMap, tradeMap, TallyMap)
  3. Studying the test files (for futures modification on TEST CASES)
• Sean
  1. Focused on Rivetz development last week

5. Marv
   1. Omniwallet
      1. User support

State of the Layer: All Hands – Oct 31 2017

• Patrick
  1. Team developing .h definitions for classes
  2. Drafted psuedocode for marginLogic(contractsExecuted) function
  3. Hit on sub-graphing function that will be building block for both marginLogic and settleContract functions.
• Zathras
  1. Omni Explorer:
     1. New optimized infrastructure finished & ready to go!
     2. Switch to new infra will occur when Adam is back on deck
  2. Omni Core:
     1. Minor tweaks to UIT prototype
• Ale/Lihki
  1. With dexx’s help drafted guide for how-to add new transactions editing a series of boilerplate files
  2. Defined draft .h file for three key classes and member functions/data
  3. Figuring out data model

State of the Layer: All Hands – Oct 24 2017