[ANN] Buzzer - Decentralized social media platform

[harapagornis]

Ah. Well, i removed it from the computer. I will wait for further computer smarter people before reinstalling. I installed it three times. It didnt work three times. So, i assume it would have been the homedirectory - because of the problems i never changed the settings before. But i cannot show you.

[1715365352]

1715365352

[buzzer.network]

Ah. Well, i removed it from the computer. I will wait for further computer smarter people before reinstalling. I installed it three times. It didnt work three times. So, i assume it would have been the homedirectory - because of the problems i never changed the settings before. But i cannot show you.

Ok, later we'll make instant setup wizard for the node.

Thanks.

[buzzer.network]

Hi!
Buzzer App v.0.1.3.9 is live on GooglePlay (https://play.google.com/store/apps/details?id=app.buzzer.mobile). Also you can download and update through APK (https://dl.dropboxusercontent.com/s/xt55sca3cztp6mn/app.buzzer.mobile.0.1.3.9.apk).

Updated:
- Improved external link expanding (youtube and various rich media)
- Stabilization

Thanks.

[buzzer.network]

Hi!
We planning to implement bridge to the Binance Smart Chain for the QBIT and QTT. Also we decided to take participation in Binance Smart Chain Grant Program (https://hidorahacks.medium.com/bsc-grant-voting-guidelines-c8918d707af4). Now our application is already published at https://hackerlink.io/en/grant. And buy the way you can vote for our project (https://hackerlink.io/en/buidl/134) it gives us:
   a) traction,
   b) a little more publicity.

Thanks.

PS. Just for information: voting BSC contract https://bscscan.com/address/0x93cc3938ed0086986dd43743063fa917572ef310

[buzzer.network]

Hi, there!

Little explanation on how to start node and begin mining.
So, if you have computer or virtual server with Ubuntu 18.x you can join and support Buzzer network.

How-to-mine.

1. Check system requirements (https://www.buzzer.network/qbit-cryptocurrency)
1.1 Node

• Minimum (Qbit mining): 2 cores​, 2 Gb RAM, 150 Gb SDD, 10 Mbit Internet access
• Optimum (Qbit mining, Buzzer miner/validator)​: 6 cores​, 8 Gb RAM, 350 Gb SDD, 20 Mbit Internet access

1.2 Full node

• Minimum (Qbit mining, Buzzer & Cubix miner/validator, up to 500 light node or clients connectivity): 8 cores​, 16 Gb RAM, 350 Gb SDD, 50 Mbit Internet access​
• Optimum (Qbit mining, Buzzer & Cubix miner/validator, up to 1500 light node or clients connectivity)​: 16 cores​, 32 Gb RAM, 500 Tb SDD, 100 Mbit Internet access
• Maximum​ (Qbit mining, Buzzer & Cubix miner/validator, up to 3500 light node or clients connectivity): 32+ cores​, 64+ Gb RAM, 1 Tb+ SDD, 150+ Mbit Internet access

2. Download qbit daemon (https://dl.dropboxusercontent.com/s/sseqqclxu82c3dh/qbit.0.1.3.8.tar.gz)
3. Untar into ~/ or your current user home directory and follow the instructions (https://www.buzzer.network/node-download)

Thanks.

[buzzer.network]

Hi, there!

How to check your node state:

1. Network connectivity

Request:

Code:

curl --data-binary '{"jsonrpc":"1.0","id":"curltext","method":"getpeerinfo","params":[]}' -i -H 'content-type: text/plain' http://127.0.0.1:8080

Output should contains some entries:

Code:

    {
        "id": "c4c847e591b381a7e6a74acd429364e6258151ad",
        "endpoint": "45.79.183.117:31415",
        "status": "ACTIVE",
        "time": 1612433346332993,
        "outbound": true,
        "latency": 67462,
        "roles": "FULLNODE|MINER",
        "address": "52Y2LKN1WkhFBN7g1ixu7177XWKdQGhdZHQKBTc7usMtkUWHNz",
        "in_queue": 2,
        "out_queue": 0,
        "pending_queue": 0,
        "received_count": 1377019,
        "received_bytes": 757301670,
        "sent_count": 639878,
        "sent_bytes": 279314315,
        "chains": [
            {
                "dapp": "none",
                "height": 647916,
                "chain": "0000000000000000000000000000000000000000000000000000000000000001",
                "block": "ca58377d576462d3a898a4d6a2da2db81cfd2ccdf59912ad578dfac2d8cb49b8"
            },
            {
                "dapp": "buzzer",
                "height": 638103,
                "chain": "51feaabb54f42f16a5878ed3545762880a5f2d26409100438b1aa080d1a70825",
                "block": "22db931028e170d8ea5db4a57f89213b9d24cebae5d967e8a7b8219acd51d004"
            },
            {
                "dapp": "cubix",
                "height": 638216,
                "chain": "b778c9558aa0f42523b0bf956c6a4ff6035282ec3d8e87bb100f2375ceba3950",
                "block": "a8ff755a29ea403f3b1de4dcbf480ceacbfe6683f6fa65acf36e8f7920fbd733"
            },
            {
                "dapp": "buzzer",
                "height": 642821,
                "chain": "3efcdc1414ec5ac42093755978eeed4c1068dbfa134716f991b382a24920ad87",
                "block": "7bd5d4da82f13e3daefec95fdaccc52105e24eb86956e8d8712f0e4e84deb7bb"
            },
            {
                "dapp": "cubix",
                "height": 642029,
                "chain": "9e452dd7f3a2d22848e547ea93b7f73e165b6a6a2a5c9b44e298e90623fc2d9a",
                "block": "6ee72ac0d237026cd9184d91df35201146acb74b630d086974baac7e2f901f85"
            }
        ]
    },

2. State

Request:

Code:

curl --data-binary '{"jsonrpc":"1.0","id":"curltext","method":"getstate","params":[]}' -i -H 'content-type: text/plain' http://127.0.0.1:8080

Output should contains:

Code:

{
    "result": {
        "state": {
            "clients": 0,
            "peers_count": 9,
            "in_queue": 484,
            "out_queue": 0,
            "pending_queue": 0,
            "received_count": 21926,
            "received_bytes": 14860474,
            "sent_count": 23303,
            "sent_bytes": 11196023,
            "chains": [
                {
                    "dapp": "none",
                    "height": 648357,
                    "chain": "0000000000000000000000000000000000000000000000000000000000000001",
                    "block": "1379ca8afcda5f4faf47e44db06909565c91ac7d0b38a5cf0d2d6f06084de933",
                    "time": 1613221241,
                    "state": "SYNCHRONIZED"
                },
                {
                    "dapp": "buzzer",
                    "height": 638297,
                    "chain": "51feaabb54f42f16a5878ed3545762880a5f2d26409100438b1aa080d1a70825",
                    "block": "5e70ee93be167b6afec88c001e7f1cd6f766c2abea9382028fcabe0ac3a13b15",
                    "time": 1613221241,
                    "state": "SYNCHRONIZED"
                },
                {
                    "dapp": "cubix",
                    "height": 638410,
                    "chain": "b778c9558aa0f42523b0bf956c6a4ff6035282ec3d8e87bb100f2375ceba3950",
                    "block": "66b2636fb1b8a87a0bc28830f603946dbe315f6492b8af0c208aff7dc6279c4c",
                    "time": 1613221241,
                    "state": "SYNCHRONIZED"
                },
                {
                    "dapp": "buzzer",
                    "height": 643020,
                    "chain": "3efcdc1414ec5ac42093755978eeed4c1068dbfa134716f991b382a24920ad87",
                    "block": "85130b3a42558da954959131c2ba82cd79786990d7fb0f89b0a70b31b7ad7bf1",
                    "time": 1613221241,
                    "state": "SYNCHRONIZING",
                    "synchronization": {
                        "type": "PARTIAL"
                    }
                },
                {
                    "dapp": "cubix",
                    "height": 642230,
                    "chain": "9e452dd7f3a2d22848e547ea93b7f73e165b6a6a2a5c9b44e298e90623fc2d9a",
                    "block": "21eac2822ab8e1697f1ceb4c58aed007c087fd48998e8391bfdce4961f065179",
                    "time": 1613221241,
                    "state": "SYNCHRONIZED"
                }
            ]
        }
    },
}

Every shard hast its own state and synchronization status:

Code:

"state": "SYNCHRONIZING",
"synchronization": {
   "type": "PARTIAL"
}

"state" can be: SYNCHRONIZED, SYNCHRONIZING, INDEXING
"synchronization" can hold the following information:

• type: FULL, PARTIAL
• remains: in case of FULL synchronization indicates how much blocks remains to download and start indexing

[buzzer.network]

New release 0.1.3.9
https://github.com/qbit-t/qbit/releases/tag/0.1.3.9

Fixed

• -home command line behavior changed
• wallet resync issues
• balance calculation optimizations
• peer protocol processing fixed: get block headers, blocks

Thanks

[buzzer.network]

New release 0.1.3.10
https://github.com/qbit-t/qbit/releases/tag/0.1.3.10

Fixed

• wallet 'pending' balance inconsistency
• cli interactive user name recognition

Thanks

[buzzer.network]

Btw, Qbit Token smart contract deployed and verified on Binance Smart Chain - https://bscscan.com/token/0xff541b9afa0ee7e658a844db2a17468227585cea

[buzzer.network]

New release 0.1.3.11
https://github.com/qbit-t/qbit/releases/tag/0.1.3.11

Fixed

• large synchronization optimizations
• memory usage optimization during sync process

Thanks

[buzzer.network]

New release 0.1.3.12.1 - Mandatory update!
https://github.com/qbit-t/qbit/releases/tag/0.1.3.12.1

Added

• newkey REST API request: import key or create new one
• FORK: full nodes now obliged to support external connectivity, i.e. you should run your nodes with -endpoint and -port command line options and proper external port mapping on your router

Fixed

• FORK: mining algo parameters adjustments
• 0.0.0.0 and 127.0.0.1 exposing (drop your ./peers directory and restart nodes)

Two key changes:
1. now full nodes should support external connectivity
2. mining algo parameters changes: block emission goes to fast on the network, so we change it back to 5-7 secs (now it's 1-2 sec), emission and schedule was not affected, only difficulty adjustment and pow check as well

NOTICE: you have ~55 hours to update your nodes, after that hard fork will happened

Thanks

[buzzer.network]

New release 0.1.3.12.3 - Mandatory update!
https://github.com/qbit-t/qbit/releases/tag/0.1.3.12.3

Fixed

• Difficulty calculation algo: time moving weighted average now calculates on 100 latest blocks (was 25)
• Blocks from nodes with extremely not synchronized clock will not be accepted

Thanks

[buzzer.network]

New release 0.1.3.13 - Major release!
https://github.com/qbit-t/qbit/releases/tag/0.1.3.13

Added

• Buzzer desktop applications for Linux and Windows
• Major improvements for UX\UI in desktop & mobile apps

Fixed

• Overall stabilization - nodes and clients
• Synchronization issues

Thanks

[Thecryptoexpert]

Facebook started in  a similar manner. Wish you well, maybe this can burst like facebook and those who invested will be lucky

[tippytoes]

Facebook started in  a similar manner. Wish you well, maybe this can burst like facebook and those who invested will be lucky

Though it seems hard to follow the footsteps of facebook, but if they can attract some users to really utilize their platform, that would be a good start. There are countless social media channels nowadays and competing is quite a challenge. You need to provide an edge or a feature that will catch the interest of people especially these millennials. And their installs in google play is still small. They need to attract more users to use their app so it will boost their potential value in the market.