# Partecipation node configuration **URL:** \ **Category:** General\ **Created:** [October 12, 2024, 10:04am UTC](https://forum.algorand.co/t/partecipation-node-configuration/13384 "2024-10-12T10:04:26Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![scholtz](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/scholtz/32/864_2.png) [@scholtz](https://forum.algorand.co/u/scholtz)\ **Post date:** [October 13, 2024, 9:02pm UTC](https://forum.algorand.co/t/partecipation-node-configuration/13384/2 "2024-10-13T21:02:23Z")
The participation node must be online to verify the transactions. On the participation node you must run the “goal account addpartkey” which generates for any address the participation keys. The “goal account changeonlinestatus” is for those who import the private key to the participation node of the account which holds algo balance (this is not secure part). It has the limitations that you cannot do it for the accounts which you do not have mnemonic for example, and i dont think there is support in goal for multisig for example… However this second part can be done easily in javascript, in some wallets which supports adding custom participation keys, or some other web tools. The main thing is just that with your account which holds algo you sign the regkey tx with the info from the participation node and then blockchain after you submit it will add you to the VRF verifiers. And for the record AF is cooking something that if you hold 30k algo on the account, and you make your account online, you will receive some yield. --- _[View the full topic](https://forum.algorand.co/t/partecipation-node-configuration/13384)._