Service Provider Promotions again

[michaeldjeffrey]

Proto PR :: helium/proto#424
Please scrutinize the names.

Previously

• incentive_escrow_fund_bps was stored in Solana, and written to s3.
• Promotions were submitted daily, and could point at a Subscriber or Gateway.

Now

• incentive_escrow_fund_bps and promotions are stored in the metadata_db.
• Promotions are pointed to by special NFTs.
• Share logic works the same
• PromotionDaemon has been removed

Temporary metadata_db table creation

I am testing with a local table until incentive programs make it into the metadata_db proper.
Using the Column mapping and Account Structure I have the following table.

CREATE TABLE incentive_escrow_programs (
  carrier VARCHAR(255) NOT NULL,    -- Pubkey (usually base58 encoded, max length 44)
  start_ts BIGINT NOT NULL,         -- i64 mapped to BIGINT
  stop_ts BIGINT NOT NULL,          -- i64 mapped to BIGINT
  shares INTEGER NOT NULL,          -- u32 mapped to INTEGER
  bump_seed SMALLINT NOT NULL,      -- u8 mapped to SMALLINT
  name VARCHAR NOT NULL             -- string mapped to VARCHAR
);

[andymck]

i kinda like this wrapper and also dont

[michaeldjeffrey]

Agreed. The plural works at both levels. I was hoping someone might help with a better name for the proto, and the wrapper name would become clearer.