-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blockmachine Validator #88
Comments
Hi @Megaduox I'm missing a way for delegators to contact you either on chain or on your given website. Also the validator details are not present. Please update this. No need to give your uptime as we will use our monitoring system made by Felix to see what your uptime was during last epoch (or since your validator went live). |
Hi, could you maybe provide me the link to the guide you created so that we can evaluate it? |
Hi, of course here is the link
https://github.com/Block-machine/create_bitsong_validator
Пт, 26 авг. 2022 г. в 01:13, Felix ***@***.***>:
… Hi, could you maybe provide me the link to the guide you created so that
we can evaluate it?
—
Reply to this email directly, view it on GitHub
<#88 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARHIKA3I64WLAFPPMURDPDLV27VXTANCNFSM56LMUJXA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi @CommunityStaking , I Am added contact information on my website and validator details. Is everything ok? |
Hi Megaduox, great about teh contact, however I still don't see the validator details filled when I check your validator on an for example mintscan: https://www.mintscan.io/bitsong/validators/bitsongvaloper1f4z9xvfswjyss32d26z8v3ak5f97t74zj5c6ht |
Done, I'm add link to mintscan and link in the main menu to validator details block |
@CommunityStaking please check is everything ok? |
Hi @Megaduox I'm still missing the details on chain. You can check out other validators what they have there. It's up to you of course what you want to promote there. |
Hi @CommunityStaking , sorry |
All good now. No it was about the on chain data :) |
Great, thanks!
Ср, 31 авг. 2022 г. в 15:17, CommunityStaking ***@***.***>:
… All good now. No it was about the on chain data :)
—
Reply to this email directly, view it on GitHub
<#88 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARHIKA2RPPMZV3ZW2IKE7A3V35EMFANCNFSM56LMUJXA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Score: 136 |
@ctrl-Felix Hi, great! But our uptime is higher, it’s approx 98-99%, where you checked it? |
Hi @Megaduox your uptime is low because you did not run the full previous epoch (the uptimes are taken over the whole previous epoch). Assuming you will keep your uptime high it will count towards the next epoch. |
Hi, great! But our uptime is higher, it’s approx 98-99%, where you checked
it?
Чт, 1 сент. 2022 г. в 00:52, Felix ***@***.***>:
… Score: 136
https://l.ctrl-felix.de/Yv072
—
Reply to this email directly, view it on GitHub
<#88 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARHIKA4VXDQP56YBZNRHLZLV37H2JANCNFSM56LMUJXA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi, glad you answered! Of course I will add contacts and update info about
my Validator details
Вс, 21 авг. 2022 г. в 22:28, CommunityStaking ***@***.***>:
… Hi @Megaduox <https://github.com/Megaduox> I'm missing a way for
delegators to contact you either on chain or on your given website. Also
the validator details are not present. Please update this. No need to give
your uptime as we will use our monitoring system made by Felix to see what
your uptime was during last epoch (or since your validator went live).
—
Reply to this email directly, view it on GitHub
<#88 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARHIKA7JWHO35QDGBLWNV6DV2J7M3ANCNFSM56LMUJXA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Cool, thanks for explanation!
чт, 1 сент. 2022 г. в 12:17, CommunityStaking ***@***.***>:
… @ctrl-Felix <https://github.com/ctrl-Felix> Hi, great! But our uptime is
higher, it’s approx 98-99%, where you checked it?
Hi @Megaduox <https://github.com/Megaduox> your uptime is low because you
did not run the full previous epoch (the uptimes are taken over the whole
previous epoch). Assuming you will keep your uptime high it will count
towards the next epoch.
—
Reply to this email directly, view it on GitHub
<#88 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARHIKA7MQXT4BU2PO64JQY3V4BYCHANCNFSM56LMUJXA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Validator address
bitsongvaloper1f4z9xvfswjyss32d26z8v3ak5f97t74zj5c6ht
On Chain Data
Contact information
Megaduox#5860/@DmitriKulagin/[email protected]
Application categories
Uptime, Participation in the BitSong ecosystem, None core development
Details
Uptime: more than 98%
Our Cosmos contributions:
Website: blockmachine.pro
Goals
Automation of validation process, involvement of new people in the bitsong network
Timetable
The text was updated successfully, but these errors were encountered: