Search Results for “admin” – BitShares®

StakeBTS 2.1 Update and Release Notes

Lucifer — Mon, 30 Aug 2021 23:46:26 +0000

by BitShares Management Group

As promised a month ago in first announcement of bugs and updates that we will perform, StakeBTS bot update came with much more changes than we originally planned. We’ve compiled the essential highlights for you in the below, while full and very detailed readme for this project can be found on the official BitShares GitHub.

StakeBTS bot is a tool for BitShares token holders (stakeholders) to lock their tokens into a fund pool, managed under corporate terms. Users who pledge to lock amounts of tokens are provided with rewards of upto 96% APY. (8% month). These returns are made through active corporate management of market making, trading, and fee pool profits.

StakeBTS bot is ran predominantly from automations with managerial controls, some of which are described below.

CHANGELOG V2.0 HIGHLIGHTS

Enhanced whereby all future payouts occur in 30 day intervals from beginning of contract
All payout amounts will be rounded down to nearest whole BTS
User will receive receipt as memo with 1 BTS upon creating a new contract
All payouts will come from bitsharesmanagement.group
In the event of payout failure, 1 BTS will be sent with additional support info
Client sends an invalid amount or invalid memo he will be refunded less 50 BTS penalty
Manager can use bot to transfer funds to and from bittrex to brokerage account
Manager can use bot to personally loan funds to the brokerage account
New database format, all payouts are added to database at start of contract
New database format, all outbound payment details are kept as receipts

FEES

It’s recommended to use the provided form on the BTSMG website for StakeBTS. The bot charges a fee of 50 BTS and returns your funds if:

Sending invalid stake amount
Sending invalid memo
Sending admin request without being in MANAGER list
Sending admin loan_to_bmg without lifetime member (LTM) status on your account
Bot ignores bittrex to bmg and vice versa transfer requests if not LTM

StakeBTS Bot TECH

1) BALANCES AND WITHDRAWALS

in a seperate script import withdrawal and balances definitions:
unit test post_withdrawal_bittrex() and post_withdrawal_pybitshares()
unit test get_balance_bittrex() and get_balance_pybitshares()

2) BLOCK OPERATIONS LISTENER

reset database
in config.py set DEV = True
send 0.1 BTS to broker, ensure script hears it arrive to the BROKER account.
check state of receipts and stakes database tables

3) DATABASE LISTENER

in config.py set DEV = True
reset database
load old contracts:
- python3.8 import_data.py
print database contents:
- sqlite3 stake_bitshares.db
- SELECT * FROM stakes;
via sql, change the due date on a single payment to 0, see that it gets paid
- sqlite3 stake_bitshares.db
- UPDATE stakes SET due=0 WHERE client='user1234' AND number=6;
check state of receipts and stakes database tables

4) REPLAY BLOCKS

reset database
in config.py set DEV = True
in config.py test True, False, int() of REPLAY
ensure script starts at correct block number
script should not create duplicates in stakes database when replaying
check state of receipts and stakes database tables

5) CLIENT MEMOS

reset database
with config.py set DEV = False and 100 added to the list of INVEST_AMOUNTS
send an invalid amount 99
send an invalid memo fail_memo
send a valid amount 100 and valid memo to start a new stake
send memo to stop a stake

6) ADMIN MEMOS

using a MANAGER account test admin memos (with and without LTM)
bmg_to_bittrex
bittrex_to_bmg
loan_to_bmg
check state of receipts and stakes database tables

7) BITTREX COVER

reset database
send 1000 BTS to Bittrex
with config.py set DEV = False and 100 added to the list of INVEST_AMOUNTS
insert line item in stakes table with amount ~500 BTS more than balance of BROKER:
- INSERT INTO
- (client, token, amount, type, start, due, processed, status, block_start, block_processed, number)
- ('user1234', 'BTS', BALANCE_BROKER, 'interest', 0, 0, 0, 'pending', 0, 0, 1)
empty the broker account
send memo to stop a stake
bot should move funds from bittrex to pybitshares wallet, then to client to cover
ideally this should be tested with various amounts in all 3 Bittrex wallets

FEATURES

automatically move funds from bittrex to hot wallet to cover payments due
does not allow non-ltm users to administrate
allows replay from current block, last block in database, or user specified block.
prevents double entries during replay

StakeBTS Public proof of 2nd round of Nominator rewards (Source: BitShares open-source wallet)

Other StakeBTS Bot Features

Automatically move funds from bittrex to hot wallet to cover payments due
Does not allow non-LTM users to administrate
Allows replay from current block, last block in database, or user specified block.
Prevents double entries during replay

Author

Concept design and logic

Sponsor

This software is sponsored and managed by BitShares Management Group Limited

Developers

v1.0 initial prototype

v2.0 refactor, refinement, added features

Conclusion

StakeBTS has come from a humble start to a polished automation platform for the holders of BTS who were never rewarded in the past – in just a few short weeks. All credit goes to the development and BitShares Management Group for the initiative, legal coverage and delivery of this project. For more about the rise of BitShares technology, see the recent publications linked in the below, and on the BitShares News website.

https://twitter.com/BitSharesOrg/status/1427470320852561922?s=20

Delegated Proof of Stake Consensus

Lucifer — Fri, 06 Aug 2021 07:40:22 +0000

Background

Delegated Proof-of-Stake (DPoS) consensus is a fast, efficient, decentralized, and highly flexible blockchain design. The BitShares blockchain leverages the power of stakeholder approval voting, to resolve consensus issues in a manner which is democratic and fair. All network parameters, from fee schedules to block intervals and transaction sizes, can be tuned via elected delegates (Committee). Deterministic selection of block producers (Witnesses) allows transactions to be confirmed in an average of just 1 second. Perhaps most importantly, the consensus protocol is designed to protect all participants in a free and fair, transparent environment.

BitShares is first and foremost a globally distributed database that is used as a ledger to track ownership of digital assets. To allow the database to remain consistent and universally agreed upon, all updates must be validated and applied in the proper order. Reaching a consensus over every ledger update is the purpose of Delegated Proof-of-Stake (DPoS).

Overview

The questions that must be answered by any consensus process include, but are not limited to:

Who will produce the next block of updates to apply to the database?
When will the next block be produced?
What transactions should be included in the next block?
How are changes to the blockchain protocol applied?
How should competing transaction histories be resolved?

By answering these questions, the goal of the BitShares blockchain is to ensure the consensus process is robust against attackers gaining control over the Delegated Proof-of-Stake network. In practice, control means acquiring the ability to unilaterally censor transactions (and corrupt or centralize the consensus protocol). The process must be autonomous against any inconsistency attack to the database state on different computers.

Block Production by Elected Witnesses

The term witness was chosen because it is a literal metaphor and noun which describes the autonomous function of the ‘Witness Node’ servers, and those elected to operate them. Witness also happens to be a legally neutral word, free from trademark or brand copyrights. Traditional contracts often have a place for witnesses to sign. For extremely important contracts, a public notary is sometimes used. Neither are party to the contract, but they serve a very important role of certifying that the contract was signed by the specified individuals at the specified time. In BitShares, witnesses serve a similar role of validating signatures and timestamping transactions by including them in blocks.

Under Delegated Proof-of-Stake (DPoS), the stakeholders can elect any number of witnesses to generate blocks. A block is a group of transactions which update the state of the database. Each account is allowed one vote per share per witness, a process known as approval voting. The top N witnesses by total approval are selected. (N) is defined such that at least 50% of voting stakeholders believe there is enough decentralization. When stakeholders express a desired number of witnesses, they should also vote for at least that many. A stakeholder cannot vote for more decentralization for which they actually cast votes.

Each time a witness produces a block, they are paid for their services. Their pay rate is set by the stakeholders via the elected delegates. If a witness fails to produce a block, they are not paid. The record of missed blocks is kept, and may lead to a witness becoming voted out in the future.

The slate of active witnesses is updated once every maintenance interval (1 day) when the votes are tallied. They are then shuffled, and each witness given a turn to produce a block at a fixed schedule of one block every 2 seconds. After all the witnesses have had a turn, they are shuffled again. If a witness does not produce a block in their time slot, then that time slot is skipped, and the next witness produces the next block.

Historically, BitShares has maintained a 99% witness participation rate. Anyone can monitor the network health by observing this metric. Any time witness participation falls below a certain level, users of the network can allow more time for transactions to confirm, and be extra vigilant about their network connectivity. This property gives BitShares the unique advantage of being able to alert users of a potential problem within 1 minute of it occuring.

Parameter Changes by Elected Delegates – Committee

Delegates known as the ‘Committee’ can also be elected in BitShares. The delegates each become a co-signer on a special account that has the privilege of proposing changes to the network parameters. This account is known as the genesis account. These parameters include everything from transaction fees, to block sizes, witness pay, and block intervals. After the majority of delegates have approved a proposed change, the stakeholders are granted a 2 week review period. During the review, stakeholders may vote out delegated committee members and nullify the proposed changes. The Committee are unpaid, however the parameters are not changed very often. (note – please see 2020 update also Sustenance of Blockchain funds).

This design was chosen to ensure that delegates technically have no direct power, and all network parameter changes are ultimately approved only by the stakeholders. With this delegated Proof-of-Stake, we can truly say that the administrative authority is fully decentralized and in the hands of the users (BTS token holders), and not the delegates nor the witnesses.

The genesis account can technically perform any action that any other account can perform. This means it is possible to send funds to the genesis account or specify the genesis account as an escrow agent. The genesis account can also be used to issue new assets. This method provides a very high degree of trust and accountability, which creates an untold number of applications whereby elected delegates can perform tasks to aid stakeholders.

Changing the Rules (aka Hard-Forks)

From time to time, it is necessary to upgrade a network to add new features. Under DPoS, all changes must be triggered by active stakeholder approval. While it is technically possible for the witnesses to collude and change their software unilaterally, it is not in their interest to do so. A witness is selected based upon their commitment to remain neutral to blockchain policy, which protects them against false allegations they are the administrators/managers/owners/operators of the network. A witness is merely an employee of the stakeholders.

Developers may implement whatever changes they deem appropriate, so long as those changes are contingent upon stakeholder approval. This policy protects the developers as much as it protects the stakeholders and ensures that no individual has unilateral control over the direction of the network.

The threshold for changing the rules is the same as replacing 51% of the elected witnesses. The more stakeholder participation in electing witnesses, the harder it becomes to change the rules.

Ultimately, changing the rules depends upon everyone on the network to upgrade their software, and no blockchain level protocol can enforce how rules are changed. This means that hard-forking “bug fixes” can be rolled out without requiring a vote of the stakeholders, so long as they remain true to the universally expected behavior of the code.

In practice, only security critical hard-forks should be implemented in such a manner. The developers and witnesses should wait for the stakeholders to approve even the most minor changes.

Double Spend Attack

A double spend can occur anytime a blockchain reorganization excludes a previously included transaction. For instance, the witnesses have a communication breakdown caused by a brief global Internet disruption. With DPoS, the probability of a communication breakdown enabling a double spend attack is very low. The network can immediately detect any loss in communication, as witnesses fail to produce the blocks on schedule. The network can throttle itself so users have to wait until half of the witnesses have confirmed their transactions, which could be up to a minute or two.

Transactions as Proof-of-Stake

Each transaction on the network may optionally include the hash of a recent block. If this is done, the signer of the transaction can be confident that their transaction may not be applied to any blockchain instance that does not include that block. A side effect of this process is that, over time, all stakeholders end up directly certifying the long-term integrity of the transaction history.

Blockchain Reorganizations

Because all witnesses are elected, highly accountable, and granted dedicated time slots to produce blocks, there are rarely any situations where two competing chains can co-exist. From time to time, network latency will prevent one witness from receiving the prior block in time. If this happens, the next witness will resolve the issue by building on whichever block they received first. With 99% witness participation, a transaction has a 99% chance of being confirmed after reaching a single witness.

While the system is robust against natural chain reorganization events, there is still some potential for software bugs, network interruptions, or an incompetent or malicious witness to create multiple competing histories longer than a block or two. The software always selects the blockchain with the highest witness participation rate. A witness operating on their own can only produce one block per round, and it will always have a lower participation rate than the majority. There is nothing that any witness (or minority group of witnesses) can do to produce a blockchain with a higher participation rate. The participation rate is calculated by comparing the expected number of blocks produced vs the actual number of blocks produced.

Maximally Decentralized

Under DPOS, every stakeholder has influence that is directly proportional to their stake, and no stakeholders are excluded from exercising this influence. Every other consensus system on the market excludes the vast majority of stakeholders from participating. There are many different ways that alternatives exclude stakeholders. Some alternatives use invite-only systems. Others exclude participation by making it cost more to participate than they earn. Still other systems technically allow everyone to participate, but they can be safely ignored by a few large players who produce the vast majority of all blocks. Only DPOS ensures even distribution of block production among the most people, and that everyone has a viable means to influence who those people are.

Fraud/Scam Warning: Trademark, Defamatory Content,’bitsharesinvest.com’

Lucifer — Thu, 29 Jul 2021 06:14:30 +0000

Legal action via trademark and copyright holder Move Institute is underway.

It’s clear this website is an intentional scam/fraud. So poorly executed, yet unfortunately, we received intelligence some may have fallen for it. Therefore we have no choice other than to try and warn as many as possible by publishing this notice. Please always keep an eye open on Crypto websites offering investments, if they’re full of obvious typing errors, bad English, and poor coding – it’s probably fake. Worth reporting if they are asking you to invest anything!

One of the reasons brand trademarking is so important in a Crypto or any other venture, is it protects users and the public. If it’s not from the proper trademark-owner sources, we hope people won’t fall for it. Sadly they still do. Some folks become blind-sided as they seek lax entry points to Crypto profits. Please don’t fall into that trap.

Red flags are obvious to you or anyone landing on this site. Regardless, BitShares will take action using our globally recognized trademark intellectual property rights. In which case, whoever created this site could be about to get a surprise. With a team of advanced coders and admins around the real BitShares team, it doesn’t take much to dig a whole lot up about a site like this. From there, a report will be lodged with appropriate authorities.

BE AWARE! Remember you can always report any scams you find to us also, we will take every action in our power to remove them. In case you don’t want to visit such a nefarious site, screenshot below so you can see how bad it is. Note the lack of buttons spacing, cheap and nasty fonts, bad spellings. Big Red flags already!

You will always have small money if you invest on fake copycat scam sites like the one featured today.

Be Aware!

If you think the above is bad, wait till you see the sign up page for even more fun – Buttons and menus all over the place, links to Privacy and Terms go nowhere!

ALWAYS – Check the Terms of your investment! In this case, there are no terms, just a dead link.

ADVICE/WARNING: DO NOT INVEST OR DEPOSIT ANYTHING TO BITSHARESINVEST.COM AS THAT IS NOT TRADEMARK APPROVED OR EVEN AUTHENTIC WEBSITE OF ORIGINAL BITSHARES ORGANIZATION!!

Privacy Policy

Lucifer — Thu, 22 Apr 2021 17:29:57 +0000

Who we are

Suggested text: Our website address is: https://bitshares.org/.

Comments

Suggested text: When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.

An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.

Media

Suggested text: If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.

Cookies

Suggested text: If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.

If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.

When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select “Remember Me”, your login will persist for two weeks. If you log out of your account, the login cookies will be removed.

If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.

Embedded content from other websites

Suggested text: Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.

These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.

Who we share your data with

Suggested text: If you request a password reset, your IP address will be included in the reset email.

How long we retain your data

Suggested text: If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.

For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.

What rights you have over your data

Suggested text: If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.

Where we send your data

Suggested text: Visitor comments may be checked through an automated spam detection service.

We are the BitShares

Lucifer — Mon, 04 Jun 2018 09:46:26 +0000

Ethics + Moral + Common Vision = Success

The achievements of an organization are the results of the combined effort of each individual.

Vincent Thomas Lombardi

Abitmore

Head of Development

Abit is one of the pioneer early developers in the BitShares community, involved since at least 2014. He also contributes to the STEEM blockchain. An advanced programmer with 91 GitHub repos, Abit is a well-respected developer among both communities.

Abdussamet Tek

Community Developer

Alex is an experienced full stack developer and has filled a variety of roles in his broad background in technology companies. For BitShares, his involvement on the governance team and lead on development activities has been significant.

Aleksandar Lakic

Strategic Venture Advisor

Aleksandar's extensive knowledge and ability to perform, analyze, calculate and research beyond public means - brings most valuable input for the top tier management.

Anton Kabalskii

CEO/President BitShares Holdings

Anton is experienced marketer, advocate for financial freedom and DLT's and has a vast experience in corporate management.

Bo Shen

Founder of Invictus Innovations

Bo Shen is a co-founder and general partner at Fenbushi Capital, an Asia-based venture capital firm that specializes in investing in blockchain technology and cryptocurrency companies. He is also a co-founder of Invictus Innovations, the team behind BitShares.

BitProfessor

Austrian Economics Believer

BitProfessor is a believer in Austrian economics and a free economy. He studied Computer Science, and has an MBA. Furthermore, developed an automatic mortgage robot and a triangular arbitrage robot using python, python-bitshares and uptick. Involved in BitShares since 2017.

Magnus Anderson

Project Manager

Magnus is an experienced web developer, well known in the community as ‘startail’ for several years. He’s also running STEEM and BitShares witness nodes, where he puts his additional 15 years of server management experience to good use.

Dr. Christopher Sanborn

Core Developer

Dr. Sanborn has been passionate about blockchain since 2013, and contributing to the BitShares ecosystem since 2017. He brings deep technical skills with his background in scientific computing and 2 decades of software development experience.

DOMINIC BARNARD

Dominic is a web designer and contributor to the bitshares wallet reference implementation.

IVAN VLAJKOVIC

Ivan is, among many other things, a strong supporter and BitShares enthusiast.

Dr.-Ing. Fabian Schuh

Developer

Fabian is an entrepreneur and fervent blockchain advocate. He came into contact with cryptocurrencies in early 2011, and was fascinated by their autonomous nature. A big believer in the implications of blockchain for value transfer and freedom of speech.

JERRY LIU

Jerry is a blockchain enthusiast and one of the earliest people to popularize BitShares in China.

JONATHAN BAHA`I

Jonathan is an advocate for decentralization and a blockchain and crypto influencer.

Yushan Zheng

Yushan graduated from University of Montreal and is acting as an executive member of Graphene Application Center and a council member of BitShares (among other things).

Milos Preocanin

General Manager

Born in Serbia, became a master of Linux networking and administration before reaching his 20’s. Apparently with a sixth sense for business and logical analysis. Since joining BitShares in 2017, has rapidly established a high-level reputation in the community.

Nathan Hourt

Core Developer

Nathan is a full stack developer and one of the original developers and architects of the Graphene Toolkit and BitShares core.

LITEPRESENCE

Litepresence is a Python developer and active community member who has made many contributions to the BitShares ecosystem.

LONG JIE

Long is a BitShares JS Developer and contributed to the development and deployment of dBTS.

LUNEDIO

xxx

QING FENG

ANDROID DEVELOPER

Qingfeng was an early advocate of blockchain, and also began researching BitShares in 2017. With extensive front-end development experience and expertise in Ruby and Ruby on Rails, he is currently responsible for the Android version of the btspp App.

NOBLENOBERT

NOBLENORBERT is author and BitShares promotor at BitShares Nigeria.

xxxx xxx

Chief Translator and Proofreader

xxxx

MICHAEL TAGGART

Michael is president of Cryptonomex, the company that authored the Graphene blockchain.

Stefan Schiessl

Release Management

Stefan transferred his strong applied mathematics background to developing and managing software development in 2005, then blockchain in 2017. He relishes the challenge of translating and abstracting complex real-world problems into manageable solutions.

Ross Walker

Content Manager, Sysadmin

Ross is an IT entrepreneur with 20 years’ experience, previously from the Telecoms industry and based in Southeast Asia since 2004. Into BitShares since 2017, Ross keeps busy managing a number of websites and writing content on various technical and hobby topics.

STAN LARIMER

Stan is co-founder of BitShares and Cryptonomex, some call him the “BitShares Godfather”.

TAMAMI SUGIMOTO

Lead Documentation Specialist, QA/Tester

T. Sugimoto is a systems analyst, programmer, web designer. Proficient in both web content management and analyzing system code in many programming languages. Over the past two years she has been creating and revising documentation for BitShares.

Yana Raduga

Operating officer of XBTS DEX

As COO of XBTS DEX, Europa leads operations relating to strategy, product management, business development and community engagement, partnership building. Europa is a member of the BitShares committee and a respected member of the community. With an curiosity and a passion for improving, she continues to teach herself new blockchain, DeFi, GameFi fields of expertise for application of decentralized technologies in the modern world.

Vvk

Supporting Dev, Contribution Auditor

Vvk has been in the BitShares community since 2017 and is an experienced GitHub maintainer. With experience across Linux, scripting, and open source software, and having worked as a sysadmin since 2004, he’s contributed to lots of open source projects over time.

Yang Ming

Designer / Tester

Yangming comes from a traditional financial and service industry background, with a keen eye for detail and insight into user experience. In the past two years, he has been working on the analysis of BitShares and created the btspp team together with Syalon.

TechnoL0g

Full-Stack

Developer 20+ years. Programming Languages & Frameworks: RUST, JAVA, JS (VUE,React,Electron,Fabric JS), C++v, C#, Assembler, Python, Sql.