I have added another backup witness server and thus having four servers in total now for the steem blockchain.

// Latest fleet: https://steemyy.com/witness-nodes.php

All servers are in good health - and closely monitored. It is important that you have different key pairs on different servers, so you can easily switch to backup servers in case the main one upgrading e.g. replaying. Double signing usually happens if you have the same key pairs on two servers, both trying to produce a block.

I hope this helps!

Steem On!~

If you like my work, please consider voting for me, thanks!
https://steemit.com/~witnesses type in justyy and click VOTE

Alternatively, you could proxy to me if you are too lazy to vote!

Also: you can vote me at the tool I made: https://steemyy.com/witness-voting/?witness=justyy

Visit me at: https://steemyy.com

This page is synchronized from the post: ‘Witness Category: a Backup Witness Node Added’

A month ago, @onepercentbetter asks for a feature:

I have improved the tool today - and have added this feature. The users can specify Recipents in the format of:

# account amount unit memo
# the following are all valid examples
justyy
justyy 0.001
justyy 0.001 STEEM
justyy 0.001 SBD
justyy 0.001 SBD HELLO [username]

Default parameters will be used if not specified at each line.

Wallet Tool: https://steemyy.com/wallet/
Same changes/improvements have been applied to Chinese version: https://steemyy.com/wallet-tool/

Use this on HIVE?

This tool supports HIVE/HBD but this feature is not fully tested (confirmed by @crypto.piotr it is working)
You would need to change the Node URL to whatever HIVE blockchain uses.

I hope this helps!

Steem On!~

If you like my work, please consider voting for me, thanks!
https://steemit.com/~witnesses type in justyy and click VOTE

Alternatively, you could proxy to me if you are too lazy to vote!

Also: you can vote me at the tool I made: https://steemyy.com/witness-voting/?witness=justyy

Visit me at: https://steemyy.com

This page is synchronized from the post: ‘Wallet Tool Upgrade: Customize Parameters for Each Recipents’

Hello,
I spent half day, started working last night and coding till 4:AM this morning.
Here you go: A Free Account Registration Tool for STEEM!

English: https://steemyy.com/reg.php
Chinese: https://steemyy.com/steemit-tools/reg.php

Account registration is not free. It costs something on steem blockchain either RC (resource credits) or 3 STEEMs. That is why we need to verify your email address and take precaution measures to reduce the spam.

1. Fill the Registration Form
2. Wait for Email
3. Click the Link in the Email to Verify
4. Wait for Account/Password in the Email
5. Recommended: Change Password as soon as you have it.

I hope this helps!

Steem On!~

If you like my work, please consider voting for me, thanks!
https://steemit.com/~witnesses type in justyy and click VOTE

Alternatively, you could proxy to me if you are too lazy to vote!

Also: you can vote me at the tool I made: https://steemyy.com/witness-voting/?witness=justyy

Visit me at: https://steemyy.com

This page is synchronized from the post: ‘Free Account Registration Service for STEEM! 免费注册 STEEM 帐号！’

A while ago, I implemented this tool: https://steemyy.com/mutual-witness/ which allows you to see who you vote, who also vote you back, and who hasn’t.

The API was based on SteemSQL but fortunately, this can be easily replaced using SteemJS.

The following SteemJS search the proxy chain:

1
2
3
4
5
6
7
8
9
10
11
12
13
14

async function getWitnessProxy(id) {
    return new Promise((resolve, reject) => {
        steem.api.getAccounts([id], async function(err, result) {
            if (err || (!result) || (!result[0]) || (result.length === 0)) {
                resolve("");
            }
            if (result && result[0] && result[0].proxy) {
                const data = await getWitnessProxy(result[0].proxy);
                resolve(result[0].proxy + " " + data);
            }  
            resolve("");
        });
    });
}

The API: https://steemyy.com/api/steemit/witness_voters/?cached&id=STEEM_ID will return the following JSON object.

1
2
3
4
5
6

{
  votes: [],   // who you vote
  both: [],    // and who have voted you back
  not: [],      // and who haven't voted you back
  proxy_chain: []    // the proxy chain separated by space.
}

You can invoke the API via GET or POST by passing the parameter id.

The GUI tool that calls the API looks something like this: https://steemyy.com/mutual-witness/?id=justyy

I hope this helps!

Steem On!~

If you like my work, please consider voting for me, thanks!
https://steemit.com/~witnesses type in justyy and click VOTE

Alternatively, you could proxy to me if you are too lazy to vote!

Also: you can vote me at the tool I made: https://steemyy.com/witness-voting/?witness=justyy

Visit me at: https://steemyy.com

This page is synchronized from the post: ‘API/Tool Update: Steem Mutual Witness Report’

From now, you can query the API /api/steemit/account/validate-user/ to retrieve the status of a steem account name.

For example:

curl -s -X POST “https://steemyy.com/api/steemit/account/validate-user/“ -d “id=justyy”

This will return:

{“accountName”:”justyy”,”result”:”taken”}

If a username is invalid, e.g.

curl -s -X POST “https://steemyy.com/api/steemit/account/validate-user/“ -d “id=123”

This will return:

{“accountName”:”123”,”result”:”Account name should start with a letter.”}

Otherwise:

curl -s -X POST “https://steemyy.com/api/steemit/account/validate-user/“ -d “id=justyy12345”

if a user account is not existent (meaning that it is available)

{“accountName”:”justyy12345”,”result”:”good”}

I hope this helps!

Steem On!~

If you like my work, please consider voting for me, thanks!
https://steemit.com/~witnesses type in justyy and click VOTE

Alternatively, you could proxy to me if you are too lazy to vote!

Also: you can vote me at the tool I made: https://steemyy.com/witness-voting/?witness=justyy

Visit me at: https://steemyy.com

This page is synchronized from the post: ‘Added API to check if a Steem UserName is taken’

Two days ago, I got an email which worries me:

With this newsletter, we want to inform you about an upcoming maintenance date in our Nuremberg data centre.

The maintenance will take place on Wednesday, 29th April 2020, at 05:30 am UTC+2

The maintenance will require a short interruption of the Internet uplink, we expect an offtime of less than 15 minutes.

The unavailability will only affect the Internet connection, your server/VPS will keep running throughout the maintenance and will be available immediately after we have completed the maintenance.

No action is required from you. This e-mail has only been sent to inform you ahead of time.

All my 3 Nodes are in the same physical location, and thus affected. Immediately, to avoid Single-Point-Of-Failure, I rented another server (Dedicated Server!) in North USA.

And it just replaced one of my Servers in Germany as the main Witness Node within 2 Days! It wasn’t ready before the maintainance event, but I was lucky to miss only 1 block!

Here is my updated node information: from https://steemyy.com/witness-nodes.php

To avoid single-point-of-failure, it is usually a good advice not to have servers in one single physical location - this is a lesson to learn from this incident (missing one block).

PS: I got the dedicated server from Dacentec.

I hope this helps!

Steem On!~

// Posted at here as well.

If you like my work, please consider voting for me, thanks!
https://steemit.com/~witnesses type in justyy and click VOTE

Alternatively, you could proxy to me if you are too lazy to vote!

Also: you can vote me at the tool I made: https://steemyy.com/witness-voting/?witness=justyy

Visit me at: https://steemyy.com

This page is synchronized from the post: ‘Witness Infrastructure Update: Adding a Witness Node in North USA to Avoid Single-Point-of-Failure’