RE: Multisig 2FA bot (Beta) by honeydue

`author`	honeydue
`permlink`	re-stoodkev-sle4j5
`category`	multisig
`json_metadata`	{"tags":["multisig"],"app":"peakd/2024.9.16","image":[],"users":[]}
`created`	2024-10-15 09:18:42
`last_update`	2024-10-15 09:18:42
`depth`	1
`children`	1
`last_payout`	2024-10-22 09:18:42
`cashout_time`	1969-12-31 23:59:59
`total_payout_value`	0.808 HBD
`curator_payout_value`	0.808 HBD
`pending_payout_value`	0.000 HBD
`promoted`	0.000 HBD
`body_length`	121
`author_reputation`	879,862,238,784,599
`root_title`	"Multisig 2FA bot (Beta)"
`beneficiaries`	`[]`
`max_accepted_payout`	1,000,000.000 HBD
`percent_hbd`	10,000
`post_id`	137,866,779
`net_rshares`	5,543,410,544,379
`author_curate_reward`	""

voter	weight	wgt%	rshares	pct	time
stoodkev	0 B		5,543,410,544,379	20%

voter

weight

wgt%

rshares

pct

time

stoodkev

0 B

5,543,410,544,379

20%

@stoodkev · Oct 16 '24

You're welcome!
Yeah, there is nothing too technical in there, the only thing is to properly understand how authority heights and thresholds work on Multisig.
Basically, a normal account has a single key with a weight and threshold set as 1 so it can sign and broadcast directly.
When using 2FA, your own key and the 2FA bot both have an authority weight of 1 and the threshold is set as 2. So it will need both signatures before being broadcasted. And the bot will only sign if the OTP is correct. That's it.

properties (22)