Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Ammar Yousef (ioBanker)

Pages: [1] 2 3 4 5
1
General Discussion / Re: Analysis of My Bitshares transaction blunder
« on: December 02, 2020, 06:53:52 pm »
Yesterday  at about 15:00 Nigerian time, I accidentally sent 15000BTS to a fake binance wallet  https://bts.ai/tx/d155375c023afafe01a892c5616a191effd02ed8 ;  binanace-bts-1 instead of binance-bts-1 the extra letter 'a' cost me to lose over half my life's worth...
Much of this cosmic comical error is attributed to my negligence and mental temprament which admittedly at the time of making this transaction was unstable (No right thinking person would make this mistake). However 10% of the blame falls on the bitshares UI I used to make the transfer. I say 10% because I still would have confirmed the transaction 9 out of 10 times due to the aforementioned conditions. The confirmation write up on the UI was too tiny to read and there was no clear way to know if I was sending to the wrong wallet unless with proper analysis.

That being said my Gross inability to perform a simple copy and paste operation was ultimately my undoing and no fault of anyone but myself... My advice to Bridge exchanges is to improve the send function of their UI by making the write up more legible and by adding an extra feature called favorite wallets, so that users that want to perform familiar transactions can easily do so without much scrutiny and mistakes.... Also a new option to make memo transactions compulsory should be added, this is to avoid sending BTS to external wallets without memo...

I sincerely apologise to everyone at Bitshares who have been supportive of my project and I promise to do better next time...
The project will now be on halt for now due to liquidity issues until my position improves...

Sorry for hearing it was a big loss to you; mistakes on Blockchain are expensive usually, please be-careful next time and review every single character you write before you submit your inputs at any blockchain.

2
Stakeholder Proposals / Re: [Witness Proposal] blckchnd
« on: November 13, 2020, 05:37:57 pm »
After abit trojan took place yesterday we've stopped our witness infrastructure for bitshares.

We have a capable team of core and UI devs, so we're preparing a fork of bitshares code base, back to the consensus rules that was before the abit abuse on github.
It will be a new distribution, a new chain, and a new genesis.
 
News will come latter with announcements.

Hello everyone!

Those of you who are following the Bitshares platform certainly know about the recent event, that caused a lot of debate. During the BTS4.0 protocol upgrade, one of the hired core devs (abitmore) added a community unapproved backdoor to the code, which led to the change of the voting rights, and a major change of the consensus procedure. As a result multiple conflicts ensued with a significant portion of chinese community leaving Bitshares.

After thoroughly analysing the consensus changes, that were made without voting or any discussion by community members, we verified that the resulting system is unscalable and doomed to stagnate. As a result our team decided to launch a fork of stable and time tested Bitshares3.0 consensus code using Graphene — the original name of the technology.

Graphene is the industrial grade technology, adapted both for private and company use. For years it was a foundation for the unique ecosystem and market economy. Its open source code and MIT license allow for creation and maintenance of different decentralized blockchain applications with workers system, that allows core token holders to elect which development to support.

To avoid the mistakes that resulted in the current status quo in Bitshares, we’ve reduced the maximum supply of GPH tokens, and decided to hold the initial distribution of Graphene tokens via all win and provably fair lottery.
The lottery would distribute 40 out of 100 million tokens, with further 60 million used in the reserve fund. The distributed tokens will form the genesis block of the Graphene blockchain, and all undistributed tokens from the 40 million will be burned.
Final supply will be formed out of the resulting sum (reserve fund + distributed tokens); 6% of that supply will be vested to the launch team with the following ratio: 1% will become available to the team within the first week of the launch, and the remaining 5% will be vested over the next 10 years.


GPH token has a limited supply, which differs from the liquid circulating supply. 60 million tokens are set aside for financing projects and block producer rewards. These funds will be available to the worker system only from GPH token holders approval. This working budget is known as “reserve pool”.
It is worth mentioning that transaction fees are not distributed among the GPH token holders, but are returned to the worker budget to pay for further development. There is no reward for holding the GPH core token in your wallet.

## About lottery

The lottery starts on the RuDEX platform concurrently with the publication of this announcement and will last for 40 days. Every days only 100,000 lottery tickets will be available, and with the end of the lottery period all undistributed tokens will be burned, with the final supply and genesis block of the new blockchain being formed as the result.

To participate in the lottery, you will have to buy a lotto ticket and register it.

Every registered ticket will allow you to win from 1 to 30 GPH tokens. For ease and transparency the lottery will be held on the Bitshares blockchain.

There are only 5 possible winning combinations with a fixed amount of tokens for each combination, as follows:

0 - 1
1 - 3
2 - 6
3 - 10
4 - 30

The combination number (0-4) will be calculated from the transaction hash on the ticket registration.

To demonstrate how the lottery works we will use RUDEX.LOTTERY token as an example.
As you can see in this block https://bts.ai/block/53159405 bot-11 account “registered” 1 RUDEX.LOTTERY and got a transaction number TXID of d60c7ce9467043cf81acd5fdb1c5bc851d20faed.
If this value is divided by modulo 5 (number of combinations), then the remainder of the division will be the combination number of this ticket. You can verify the division remainder using, for example, the following service: https://defuse.ca/big-number-calculator.htm
In our case you need to insert the following line into the calculator 0xd60c7ce9467043cf81acd5fdb1c5bc851d20faed  % 5, which is equal to the value of 4, which is a combination for 30 GPH token win.

It is possible to register any number of tickets concurrently, which results in cycles of combinations (0-4) are counted from the division reminder value of the transaction hash until all tickets are given the result.

For your ease and convenience the lottery page display the transaction hashes and results for all of your registered tickets. Every lottery result is available for a public review.

So if you are as tired of the unfair games and underhanded intrigues as we are, we are inviting you to start anew and open the Graphene technology in its original balanced and transparent nature

https://market.rudex.org/#/lottery

Your opinion about BitShares isn't credited; I don't see your initial distribution making any sense, I suggest you do some MLM schemes like selling replica watches for your GPH so it might have value.

3
You have my support Europa.

4
Stakeholder Proposals / Re: [Witness Proposal] blocksights
« on: October 07, 2020, 09:44:54 pm »
Adding your API node: wss://eu.nodes.bitshares.ws

Thanks guys.

5
Thanks.

6
Stakeholder Proposals / Re: [Witness Proposal] blckchnd
« on: October 04, 2020, 12:09:08 pm »
His CEX orderbook is not even 1% of daily volume coinmarketcap
Your CEX iobanker is even not on cmc, boy

ioBanker isn't CEX nor a gateway; stop comparing your poor startup with ioBanker, kid.

7
Stakeholder Proposals / Re: [Witness Proposal] blckchnd
« on: October 04, 2020, 05:23:43 am »
seems it's off topic far away,
I'm not interested in those gossip.
I can see rudex's effort from the order book in the past weeks,
Wish rudex could stay with Bitshares.

He will stay don't worry; he cannot trust NBS airport to run his free database and application server.

His CEX orderbook is not even 1% of daily volume https://coinmarketcap.com/currencies/bitshares/markets and his harassments to BitShares community wouldn't be justified nor forgiven.

8
Stakeholder Proposals / Re: [Witness Proposal] blckchnd
« on: October 03, 2020, 06:48:04 pm »
After abit trojan took place yesterday we've stopped our witness infrastructure for bitshares.

We have a capable team of core and UI devs, so we're preparing a fork of bitshares code base, back to the consensus rules that was before the abit abuse on github.
It will be a new distribution, a new chain, and a new genesis.
 
News will come latter with announcements.



We haven't seen your capable team of core and UI participating in any development related to BitShares as organization; your developments were obviously self-interests and private use cases ONLY; you were using the platform UI and the blockchain as a free database and application server for your CEX/Gateway use case; you never implemented new features nor fixed a single bug effecting BitShares.

There is no problem with utilizing BitShares as a free database and application server for CEX business use case; but BitShares isn't ONLY "CEX" business use case; we haven't seen any positive approach from your side nor a vision to support the ongoing development of BitShares; I had witnessed myself your FUD and attack on BitShares as if you were BitShares's competitor or enemy; spitting inside a plate that you were eating from in daily bases on Telegram with your team and supporters.

You were abusing your position as an admin on telegram, FUD, bad words and harassments; you were driving the masses to give up on BitShares while others were working on new features to change and to fix specific issues that was preventing the platform from growing.

Your failing strategy of attacking the network community, FUD, attacking developers and personalizing discussions isn't the strategy that is needed to change any facts on BitShares; BUT civilized discussions with community members which obviously you were lacking.

Some are really thinking BitShares is only a gateway/CEX application server and database engine; "CEX" decisions are self-interest naturally; BUT it isn't BitShares development. perhaps CEX voters are being paid back under the table by corrupt workers, WHY NOT; thanks to BitShares 5.0, this wouldn't be a case when voters are locking their BTS.

I believe you should stop acting as if you were important to BitShares Organization and I believe "alt" should rethink his mind about you.


9



Our Committee Blockchain Account: iobanker-core


How Do We See BitShares:

BitShares is a decentralized permissionless “Blockchain As Organization” (BAO); a powerful beyond bitcoin innovation in which its core asset BTS is being utilized as an organization proof of stake and a utility token in order to serve BitShares Blockchain users financial means in a form of transactions and contracts fully stored on each node of its decentralized network.

BitShares Blockchain is very similar to public companies or open joint-stock companies; yet it’s not required to be registered nor trusted.

BTS core asset of BitShares is used for development purposes; while BTS asset shareholders are in power to manage and develop BitShares and influence it's future using several decentralized integrated functions and tools such as decentralized worker and voting system.

BitShares is trustless, permissionless and fully managed on the internet. BitShares had enabled several blockchain functions at its single core such as DEX decentralized exchange engine, DeFi and AMM enabled assets factory and HTLC.


Our Infrastructure Contributions:

1) Public BitShares Browser based UI [ioBanker DEX]: https://dex.iobanker.com "running from Germany".
2) Public BitShares Websocket API Node wss://dex.iobanker.com/ws "running from Germany".
3) Public BitShares Rest API Node https://api.bitshares.build "running from Germany".
4) Blockchain Witness Node Witness: iobanker-core "running from Amsterdam".


Our Development Contributions:

1 - https://github.com/bitshares/bitshares-core/pull/2261
2 - https://github.com/bitshares/bitshares-ui/pull/3135
3 - https://github.com/bitshares/bitshares-core/pull/2060
4 - https://github.com/bitshares/bitshares-ui/pull/3275
5 - https://github.com/bitshares/bitshares-fc/pull/207
6 - https://github.com/bitshares/bitshares-ui/pull/3282
7 - https://github.com/bitshares/bitshares-ui/pull/3275
8 - https://github.com/bitshares/bsips/issues/202
9 - https://github.com/bitshares/bitshares-core/issues/2018
10 - https://github.com/bitshares/bsips/issues/236
11 - https://github.com/bitshares/bsips/pull/237
12 - https://github.com/bitshares/bitshares-ui/issues/3132


Creating BitShares Build Website: https://bitshares.build


Creating BitShares Build Public Rest API Swagger: https://api.bitshares.build/api-docs


Creating BitShares Docs Portal: https://docs.bitshares.build


Creating BitShares Management Public Portal: https://bitshares.management


Creating BitShares Telegram Group: https://t.me/BitSharesGroup


Developing Swap Pipeline Between BitShares and XRPL: https://ioxbank.com


Our Latest Drafted Vision: https://bitsharestalk.org/index.php?topic=29379.0


Our Target as of August 28, 2019: https://bitsharestalk.org/index.php?topic=29379.msg334496#msg334496


Our Proxy Account: bitshares-vision


For feedback: https://t.me/ioBanker or https://iobanker.com "Contact Management"



Thank you for supporting us!

10
General Discussion / Re: BitShares 5.0 (2020-09-30)
« on: September 17, 2020, 12:12:18 am »
insulting the only last active core developer on this blockchain

LoL this kind of developers as abit must be kicked out from the job as fast as possible

But I'm not surprised why you are supporting broke of the consensus and abit scam



When I look to your company I laughed hard:

https://www.e-krediidiinfo.ee/14386003-IOBANKER%20O%C3%9C

you have nice office in the middle of the forest, very "trustworthy"

Männimäe, Pudisoo küla Kuusalu vald Harju maakond 74626

did you google yourself where you registered? Take it easy I made some screenshots for you





with such "office" no surprise why you support fraud =)

I had a couple of companies in Estonia lived there for a while and when I saw the place of your company registration I laugh out loud, just FYI if it not Tallinn or Tartu 9 from 10 it is a scam, and then I google it and found your office in the middle of nowhere)))

When you don't find anything wrong with me; you will make it.

The Estonian government is controlled by an intelligent race; your kind wouldn't understand.

First of all you need classes in using Google of course; this is the official Estonian government Centre of Registers and Information Systems: https://ariregister.rik.ee go and type iobanker and hit enter to see our address; government wouldn't register us without proofing we exist there; why don't you come and give a visit? or be brave enough to write your RuDex underground address here so perhaps intelligent race would give you a visit and teach you Google :)

I'm aware that your kind wouldn't be happy when they see our work here: https://e-estonia.com/why-is-estonia-a-startup-paradise/

"TIME WILL TELL".

11
General Discussion / Re: BitShares 5.0 (2020-09-30)
« on: September 16, 2020, 11:51:30 pm »
Remove voting power from liquid BTS and tickets #2262
https://github.com/bitshares/bitshares-core/issues/2262

New BSIP or BSIP24 discussion: stake lock-up mechanism, count only real "locked" stake as voting stake #83
https://github.com/bitshares/bsips/issues/83


Maybe someone explains Abit that BTS is not Steem and that BTS is core token of our ecosystem .

So somebody who is inactive and stacking BTS has in his eyes more value in governance than somebody who is activly using bitshares ecosystem and knows the ins and outs and creates income for bitshares.
The active member having completly no say as he is using BTS in the ecosystem which is the main purpose of BTS.

Maybe Abit can explain to us how somebody who stacks only participates in bitshares growth and i'm not talking about price.


Comments from that BSIP in github

TheTaconator DEV
Quote
My main concern with the proposition is for the stake in collateral. It seems unfair to those holders to limit their influence on voting especially due to the value that their collateral brings to the ecosystem.

startailcoon UI DEV

Quote
BTS locked in collateral could be counted as locked assets. Even if it could be liquidised its also a risky business while making good volume for the bitAsset as well. It could be considered a good thing that the asset is used, and thus should be counted.

Open orders aren't locked, since they are for sale, and shouldn't be counted.

xeroc DEV

Quote
Collateral: I would argue this should be voting because it is not quickly liquidated in case the BTS valuation goes down. Also, people have been asked to go short if they really want to support the system and we would take away their voting right now. Doesn't feel right.

Quote
If we were to require a powerup to enable governance features I see the following major issues:
This changes the previous deal which has potentially been used by investors to decide to buy in. Given that BTS is much more decentralized than STEEM (there is no 'steemit inc.') this might open up the possibility for class action suites against a) the proxies who approved that change, and b) the witnesses who applied the change.

Schiessl UI DEV

Quote
Just FYI: Removing liquid BTS from voting power will strip ref UI users of their voting since you can only stake BTS with CLI.

blckchained gateway DEV

Quote
dude you went against consensus and brought trojan in previous release, as a top witness I will not support any code from you


Litepresence DEV and honest asset

Quote
The world is full of good locksmiths: some of them are unethical thieves


R DEV and security tester

Quote
Degrades BTS Utility

I could continue with the statements of honest DEV's on bitshares.

You Ammar belong to a red socket dev caste who thinks like socialist leaders who have nothing and want to control everything claiming that folk can't handle wise decissions.
That's the exect same explanation of eastern communism why they had planned econemy.
Btw you red socket proofed already on iobanker that you totaly failed.I told you a year before that noone nuts enough is going to follow an unethical dev with poor trading fundamentals and law knowledge who proofs himself untrustworthy each time on telegram.
Did something changed after a year of your spamming and garbage claims ?I guess not ?How much debt has your token now after such a long time ?Like $2K in total which you call a great success?

I am what I am; you are what you are; people around knows; you radical racist; here is BitShares, the Blockchain of diversity; a worldwide organization; built and controlled by the intelligent race; and guess what? you are not one of us and cannot control us with your fiats; we will break your fiats down like a fly; expect us.

12
General Discussion / Re: BitShares 5.0 (2020-09-30)
« on: September 16, 2020, 07:06:27 pm »
Remove voting power from liquid BTS and tickets #2262
https://github.com/bitshares/bitshares-core/issues/2262

New BSIP or BSIP24 discussion: stake lock-up mechanism, count only real "locked" stake as voting stake #83
https://github.com/bitshares/bsips/issues/83


Maybe someone explains Abit that BTS is not Steem and that BTS is core token of our ecosystem .

So somebody who is inactive and stacking BTS has in his eyes more value in governance than somebody who is activly using bitshares ecosystem and knows the ins and outs and creates income for bitshares.
The active member having completly no say as he is using BTS in the ecosystem which is the main purpose of BTS.

Maybe Abit can explain to us how somebody who stacks only participates in bitshares growth and i'm not talking about price.

Voting is used for governance purposes; governance is used for stabilizing the blockchain, it's infrastructure and development; you are not an infrastructure expert nor a developer; you don't need to be here by the way; you are claiming your self as a market expert; I doubt that too, kindly stay in market making and show us what can you do for BitShares instead of insulting the only last active core developer on this blockchain.

For those who cannot read codes nor understand development should never get involved in voting, when it comes to the changes that is proposed here; this will raise the value of BTS because BTS will be locked and any leading role in development further would require sacrificing BTS in locks; if development is failing for these voters; the future value of their BTS when it's unlocked is enough punishment for them.

13
Thanks for marketing to Onest design; deploy what you are talking about and lets see it running on BitShares.

14
公会关于4.0版本升级的声明——致所有见证人
众所周知,在BTS4.0版本升级中,个别开发人员在社区不知情的情况下,私自篡改投票系统,造成极其恶劣的影响。我们认为,这种行为践踏了BTS区块链的信任基础、撕裂了社区团结、动摇了投资者的持币信心。如果不立即纠正,BTS在区块链世界中将再无信用可言。

为此,公会开发了4.0版本补丁程序,该补丁程序目的是将投票系统恢复成4.0版本之前的状态,以消除不良影响。该补丁仅修复了未经社区投票私自增加的变更,不影响4.0版本其他功能的正常使用。

我们呼吁所有见证人安装该补丁。见证人安装该补丁文件后,该补丁文件将在北京时间2020年8月20日21:55分自动生效。

请所有见证人(包括非活跃见证人)在北京时间2020年8月15日24:00分之前在本帖下回复补丁安装情况。从北京时间2020年8月16日开始,我们将对没有回复安装补丁文件的见证人撤票,并投票给已经安装补丁文件的见证人。若支持安装补丁文件的见证人数量不足,公会将启用公会备用见证人,将见证人数量补足。

其他所有个人节点、交易所节点、重钱包也应当在20日之后安装此补丁,以免影响使用。

公会将不断致力于维护BTS区块链系统的信用、公平和正义,我们支持一切合法的、有益的系统升级。

如见证人安装补丁时有任何问题请联系微信:xiaoyuan  409

补丁下载地址:https://github.com/bitshares-cnvote/bitshares-core



Cn-vote's statement on version 4.0 Upgrade -- to all witnesses
As we all know, in the bts4.0 version upgrade, individual developers tamper with the voting system without the knowledge of the community, causing extremely bad impact. We believe that this behavior has trampled on the trust foundation of BTS blockchain, torn community unity and shaken investors' confidence in currency holding. If not corrected immediately, BTS will no longer have credibility in the blockchain world.

To this end, CN vote developed a 4.0 patch, which aims to restore the voting system to the state before version 4.0 to eliminate adverse effects.This patch only fixes the changes that are added without community voting, and does not affect the normal use of other functions of version 4.0.

We call on all witnesses to install the patch. After the witness installs the patch, the patch will automatically take effect at 21:55, August 20, 2020(Beijing time).

All witnesses (including inactive witnesses) are requested to reply to the patch installation under this post before 24:00 Beijing time on August 15, 2020. Starting from August 16, 2020, Beijing time, we will withdraw votes for witnesses who have not responded to the installation of patch files and vote for witnesses who have installed patch files. If the number of witnesses supporting the installation of patch files is insufficient, CN vote will enable the standby witness to supplement the number of witnesses.

The cn-vote will continue to be committed to maintaining the credit, fairness and justice of BTS blockchain system. We support all legal and beneficial system upgrades.

If the witness has any problems in installing the patch, please contact wechat:
 Xiaoyuan  409

Patch download address:  https://github.com/bitshares-cnvote/bitshares-core

1) You said "individual developers tamper with the voting system without the knowledge of the community, causing extremely bad impact"

what an excuse when an irresponsible admin upgrades his own node without his own knowledge about what he's writing there, I wouldn't trust or vote such an irresponsible admins.

2) You said "We believe that this behavior has trampled on the trust foundation of BTS blockchain"

The foundation wasn't there.

3) You said "BTS will no longer have credibility in the blockchain world"

BTS now is having more credibility because corruption and loopholes in voting system are patched.

4) You said "CN vote developed a 4.0 patch"

 I doubt your patch would work, if by any chance it works and your code was applied, I believe you wouldn't be able to handle the core development because everybody is aware of your poor technical skills, you might be good investors; I doubt because you couldn't bring a single development to the blockchain, non of you is well matured technical nor a businessman.

5) You said "This patch only fixes the changes that are added without community voting"

lets see how many BP admins are going to apply the patch with the same exact mistake of not having the knowledge of what they're doing.

6) You said "We call on all witnesses to install the patch"

I say I call all witnesses not to install this patch, we're done with corruption of voting power system and we don't wanna go back, you go back alone. :)

7) You said "We support all legal and beneficial system upgrades."

I say you could not benefit the system by any mean ever, it's obvious, since your first day until now you were silent about issues of voting and worker system and we haven't seen your development workers nor technicals anywhere.

Thanks for reading and sorry for my honesty.


15
I am a supporter for your great work DL...

Pages: [1] 2 3 4 5