[Witness Proposal] blocksights

[sschiessl]

The ui of Blocksights is now avaible here
    https://github.com/blocksights/blocksights-open-explorer

Please feel free to create issues for any feedback / wishes or bugs

[abit]

Found a bug.

On the account page https://blocksights.info/#/accounts/sschiessl, in the history, "better-ballot-operator-04 sent 100 BTS to sschiessl", the link on the receiver is wrong - it is "https://blocksights.info/#/assets/1.2.751875", but should be an account.

Hi Stefan, is your ES wrapper compatible with the reference UI? If yes, are you willing to add your ES wrapper address to https://github.com/bitshares/bitshares-ui/edit/develop/app/api/apiConfig.js so that others can use it directly from the reference UI?

Thanks.

Hey there abit,

it is indeed compatible with the reference UI, have a look here https://github.com/bitshares/bitshares-ui/pull/3324. Availability not guaranteed.
I have also unlocked account history export for https://blocksights.info (accounts with less than 10k operations, larger history needs promo code).

Thanks a lot.

[sschiessl]

Hi Stefan, is your ES wrapper compatible with the reference UI? If yes, are you willing to add your ES wrapper address to https://github.com/bitshares/bitshares-ui/edit/develop/app/api/apiConfig.js so that others can use it directly from the reference UI?

Thanks.

Hey there abit,

it is indeed compatible with the reference UI, have a look here https://github.com/bitshares/bitshares-ui/pull/3324. Availability not guaranteed.
I have also unlocked account history export for https://blocksights.info (accounts with less than 10k operations, larger history needs promo code).

[abit]

Hi Stefan, is your ES wrapper compatible with the reference UI? If yes, are you willing to add your ES wrapper address to https://github.com/bitshares/bitshares-ui/edit/develop/app/api/apiConfig.js so that others can use it directly from the reference UI?

Thanks.

[sschiessl]

Looking for feedback for account history export feature of blocksights.info. Preferably with people that are filing their crypto taxes to validate the format in terms of completeness.

See on the top right of the account history list
https://blocksights.info/#/accounts/sschiessl

Please contact me if interested, currently the feature is only available with a code.

[Ammar Yousef (ioBanker)]

Adding your API node: wss://eu.nodes.bitshares.ws

Thanks guys.

[BitsharesLabs]

Excellent resources

[abit]

Thanks for your contribution.

[sschiessl]

Dear BitShares Community,

we are seeking to become a block producer for the BitShares Blockchain and want to introduce our services. The "we" here refers for the technical team to Fabian (https://github.com/xeroc) and myself (Stefan, https://github.com/sschiessl-bcp).

Testnet Block Producer

Account Name:	blocksights
Account ID:	1.2.25653
Witness ID:	1.6.120
Current signing key:	TEST7CKF8GKknjvfwp7RM3vr28sZzwGM8z2zruEQwCJLpWmVvCwvis

Up and running, voted active and producing blocks since last week.

Mainnet Block Producer

Account Name:	blocksights
Account ID:	1.2.1793091
Witness ID:	1.6.180
Current signing key:	BTS8jE5q5e1NhekG7dbrzn9RunyKUCf5XkaqagfYJhtzhnHKtBr8H

Up and running, ready to be voted active.

Blocksights Explorer and API
Key service that we are providing is the Blocksights Explorer and its underlying API:

https://blocksights.info/
https://api.bitshares.ws/docs
https://api.testnet.bitshares.ws/docs

The explorer supports mainnet and testnet (switcher in the upper right corner) and will be continually improved and extended provided we get the voters backing or funds through other means. The API itselfs offers current state and historical data of the blockchain through ElasticSearch, and supports crawler endpoints for cryptoranking websites like CMC, CoinGecko, CoinPaprika, Nomics, Blocktivity and, last but not least, Feixiaohao.

Remarks:

• We do not seek to participate in price feeding as we do not see that as our area of expertise.
• At the time of writing the source code of the explorer and the API is proprietary.
• The explorer may contain bugs here and there, please let us know if you find any.

Any and all feedback on our block producer introduction or the explorer is welcome.

Happy voting!