Final Pre-Seed/Seed Investor Debt UBQ

[0x4007]

So what's next steps to watch out for? Do we need to fix the amounts again when the stakes are withdrawn?

Finally!

The next 'final' batch should be done after bonds expiry. Only then the remaining exact payout amounts will be available.

The algorithm will be:

1. Update network block number in https://github.com/gitcoindev/uad-contracts/blob/staking-mutliplier-fix/tasks/simulateBondingDebt.ts and execute the script again using the following command:

$ npx hardhat simulateBondingDebt

This will fork the blockchain, get the current inflation rate and output missing stake values for the same set of bonds. What was paid / disbursed today, should be subtracted from the amount that will be shown.

2. The BondingDebtV2 / BondingDebtFinal contract will be deployed in the same way BondingDebt, but with remaining UBQ values for the bond holders.

Originally posted by @gitcoindev in #752 (comment)

[0x4007]

@gitcoindev can you let me know when the final stake is expected to expire so I can set this on my calendar?

[gitcoindev]

@gitcoindev can you let me know when the final stake is expected to expire so I can set this on my calendar?

Yes, I will provide the date, actually this will be a block number.

I also thought about emitting a blockchain event from the BondingDebt contract when the final payout occurs, it will then be a trace that it happened.

Just noting this to myself in order not to forget:

event LogSeedUBQDebtPayout(string msg);

emit LogSeedUBQDebtPayout('Seed investor UBQ debt payout for bond holder x ');

[gitcoindev]

I collected the data in one table from the previous comments:

#752 (comment)

Bond ID	Bond holder	Bond expiry block	Estimated expiry date
1	0x89eae71B865A2A39cBa62060aB1b40bbFFaE5b0D	21124941	Mon Nov 04 2024 09:37:03 UTC
2	0x4007CE2083c7F3E18097aeB3A39bb8eC149a341d	22618922	Fri May 30 2025 20:33:51 UTC
3	0x7c76f4DB70b7E2177de10DE3e2f668daDcd11108	22624203	Sat May 31 2025 14:10:03 UTC
5	0xa53A6fE2d8Ad977aD926C485343Ba39f32D3A3F6	22647574	Tue Jun 03 2025 20:03:27 UTC
6	0xCEFD0E73cC48B0b9d4C8683E52B7d7396600AbB2	22676978	Sat Jun 07 2025 22:04:39 UTC

The dates are estimates provided by Etherscan taking into account average block time.
I think it is safe to say that the next final UBQ debt payout for all affected bond holders should happen in the first half of June 2025.

[ubiquity-os]

! Please set your wallet address with the /wallet command first and try again.

[ubiquity-os]

+ Successfully registered wallet address

[ubiquity-os]

Warning!	This task was created over 151 days ago. Please confirm that this issue specification is accurate before starting.
Deadline	Mon, Oct 7, 7:57 AM UTC
Beneficiary	0x191c51715c68Ae8F2D366b3294A82Ac28c00CAfD

Tip

• Use /wallet 0x0000...0000 if you want to update your registered payment wallet address.
• Be sure to open a draft pull request as soon as possible to communicate updates on your progress.
• Be sure to provide timely updates to us when requested, or you will be automatically unassigned from the task.

[ubiquity-os]

+ Successfully registered wallet address

[ubiquity-os]

Available Commands

Command	Description	Example
/help	List all available commands.	/help
/allow	Allows the user to modify the given label.	/allow @user1 label
/query	Returns the user's wallet, access, and multiplier information.	/query @ubiquibot
/start	Assign yourself to the issue.	/start
/stop	Unassign yourself from the issue.	/stop
/wallet	Register your wallet address for payments.	/wallet ubq.eth

[ubiquity-os]

@Apetree100122, You are not allowed to set access

[ubiquity-os]

assistive-pricing plugin failed to run.
CommanderError3: error: command-argument value 'solved' is invalid for argument 'username'. Username should start with @.

Usage:   /<command> @<username> [labels...]

Arguments:
  command        The command to execute, e.g. /allow
  username       User name to allow rights to, e.g @ubiquibot
  labels         Labels to allow, e.g time priority

Options:
  -V, --version  output the version number
  -h, --help     display help for command

[ubiquity-os]

@Apetree100122, You are not allowed to set access

[ubiquity-os]

assistive-pricing plugin failed to run.
CommanderError3: error: missing required argument 'username'

Usage:   /<command> @<username> [labels...]

Arguments:
  command        The command to execute, e.g. /allow
  username       User name to allow rights to, e.g @ubiquibot
  labels         Labels to allow, e.g time priority

Options:
  -V, --version  output the version number
  -h, --help     display help for command

[ubiquity-os]

Failed to run command-query-user.
CommanderError2: error: missing required argument 'username'

Usage: program [options] [command]

Options:
  -h, --help                   display help for command

Commands:
  /query [options] <username>
  help [command]               display help for command

[henalolp]

/help

[alexandr-masl]

/start

[ubiquity-os]

! You do not have the adequate role to start this task (your role is: member). Allowed roles are: collaborator, admin.

[alexandr-masl]

Hi everyone,
Is there a way I could get the collaborator role so I can start working on this issue?