[VPD-404]: Add PT_clisBNBx_25JUN2026 market to core pool and BNB e-mode group

[Debugger022]

Add PT-clisBNB-25JUN2026 Market to Venus BNB Chain

• Introduces PT-clisBNB-25JUN2026 as a new supply-only market in the Core Pool, borrow paused.

• Configures risk parameters:

  • supply cap 25,000,
  • borrow cap 0,
  • collateral factor 0% (core), 87% (emode),
  • liquidation threshold 0% (core), 90% (emode),
  • liquidation incentive 104% (emode).

• Sets up Pendle oracle.

• Adds the market to the BNB emode group.

• Configures conversion incentives for relevant converters.

• Includes simulation tests for mainnet and testnet.

Updated the VOTING_PERIOD to 192384 in the index.ts to account for the new block rate in the Fermi upgrade.

[GitGuru7]

please fix simulations for price check, rest looks good to me.

[GitGuru7]

BNB eMode is already active on mainnet. We can just add a check in the simulations and remove this command from the VIP.

[Debugger022]

Removed from mainnet b79dff5

[GitGuru7]

This is false by default, so we can remove this comment and just include a check in the simulations.

[Debugger022]

b79dff5

[fred-venus]

for irm, since the asset is supply only, do we really need it ? The value here are just random value ?

[Debugger022]

We have taken the IRM values the same as the asBNB market.

[fred-venus]

fine, but it won't have any actual usage, is it

[Debugger022]

@fred-venus Yes, for a supply-only market, the IRM is not functionally used, but a contract may still be assigned for protocol consistency.

[fred-venus]

For the test simulation only issue:

  1) Post-VIP behavior
       check price PT_clisBNB_25JUN2026:

      AssertionError: expected 912542998347158442194 to equal 912542911682632512322. The numerical values of the given "ethers.BigNumber" and "ethers.BigNumber" inputs were compared, and they differed.
      + expected - actual

      -912542998347158442194
      +912542911682632512322
     

But i think it's expected for PT asset, can use closeTo maybe ?

[Debugger022]

For the test simulation only issue:

  1) Post-VIP behavior
       check price PT_clisBNB_25JUN2026:

      AssertionError: expected 912542998347158442194 to equal 912542911682632512322. The numerical values of the given "ethers.BigNumber" and "ethers.BigNumber" inputs were compared, and they differed.
      + expected - actual

      -912542998347158442194
      +912542911682632512322
     

But i think it's expected for PT asset, can use closeTo maybe ?

yes it's realted to PT assest.
fixed