16
General Discussion / Re: The smallest unit of bitshares
« on: October 13, 2020, 02:23:27 pm »I use for any cryptocurrency "satoshi" as smallest unit.Satoshi is meant for BTC please choose something else
Hmm. Still easiest
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.
Hmm. Still easiest
17
General Discussion / Re: The smallest unit of bitshares
« on: October 13, 2020, 01:52:04 pm »
I use for any cryptocurrency "satoshi" as smallest unit.
18
Stakeholder Proposals / [Witness Proposal] blocksights
« on: October 07, 2020, 09:26:21 am »
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
Up and running, voted active and producing blocks since last week.
Mainnet Block Producer
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:
Any and all feedback on our block producer introduction or the explorer is welcome.
Happy voting!
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 |
Mainnet Block Producer
| Account Name: | blocksights |
| Account ID: | 1.2.1793091 |
| Witness ID: | 1.6.180 |
| Current signing key: | BTS8jE5q5e1NhekG7dbrzn9RunyKUCf5XkaqagfYJhtzhnHKtBr8H |
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!
19
General Discussion / Re: BTS中国公会关于执行补丁的公告 Announcement on Implementation of BTS CNVOTE Patch
« on: August 19, 2020, 04:42:36 am »This brings huge risks to investors, and CNVOTE retains the power to pursue further legal actions.
...
We call on all bts holders to vote in timely manner in order to form a community consensus as soon as possible.
...
In order to maintain the foundation of trust in the blockchain , CNVOTE have no choice but fighting back.
In the past risk-free margin positions (deemed temporary solution that are now more of a permanent one with the main objective of protecting debt holders it seems) and other agendas were pushed, even with the help of the voting power of CEXes, other questionable methods and without following proper voting procedures (some would call that playing dirty utilizing the tools available at hand). Attempts were made several times to point in the right direction, follow consensus guidelines and alternatives presented.
The current events are not surprising considering that. Finding a compromise will be hard with that history, but not impossible. Your statements are quite bold.
20
General Discussion / Re: Cn-vote's statement on version 4.0 Upgrade -- to all witne公会关于4.0版本升级的声明——致所有见证人
« on: August 13, 2020, 06:16:54 am »
The patch is not a straight reversal of the voting system, it is something else and it looks less stringent to me than what abit did.
21
中文 (Chinese) / Re: 4.0 投票机制变化
« on: August 03, 2020, 11:30:53 am »QuoteThey can't make a patch on BitShares for BitSharesMaybe he said is right，seems he own the trademark of “BitShares” and "BTS", if this is true, anyone can't change it.
The blockchain consensus is ultimately decided by the witnesses and what version they are running, and the voters have the indirect power over that by voting in witnesses that support whatever version they deem the correct one. It boils down to similar situation like Steem does it's consensus upgrades now, I don't see yet how the trademark affects that.
22
General Discussion / Re: So, who can tell me what happend in voting?
« on: July 30, 2020, 07:02:03 pm »
Any chance for a volunteer translator please?
The automatic translation sounds quite weird.
The automatic translation sounds quite weird.
23
Stakeholder Proposals / Re: [Worker Proposal] Bitshares UI, 2020 (6 months)
« on: May 29, 2020, 05:57:04 am »UI team more like self oriented (Pay me and I fix any small random bugs and develop some new features from Core) and BTS++ team more focus on community need(Features that highly demanded now and Bugs that blocking users having good user experience). If UI team fail to learn from BTS++ team, then nothing will change.
The approach from BTS++ team and UI team was/is quite different. BTS++ does private discussions and management to define what they do next. Advantage is that they seek proactive feedback (and also get it because they are included in chinese community), disadvantage is that there is no transparency whatsoever to the outsider (not even I would know where to look).
The UI team has done everything managed publicly through the GitHub repository (https://github.com/bitshares/bitshares-ui). The advantage is full transparency and accountability, and also a public well-defined development cycle. The disadvantage is that it was expected that the community gives feedback by opening an issue in the repository (it was always open for all, anything that I have seen I have created an issue mostly myself).
In that sense, BTS++ collects private feedback proactively, and UI team collects public feedback passive (proactive for anything that I saw). So in that sense I strongly disagree with your statement I quoted above, especially since the current worker proposal addresses your concerns.
24
Stakeholder Proposals / Re: [Worker Proposal] Bitshares UI, 2020 (6 months)
« on: May 28, 2020, 12:13:08 pm »Any estimates how much it would cost to just get the most urgent done ?
Depends how you define urgent. Node connectivity seems to be a prominent issue.
The concern is UI team fail to identify what need to be done and how much the budget.
The Core worker have list down what need to be done and maximum hours for each BSIPs.
Quite different situation. Please read the UI worker proposal, intention is laid out there.
Core is following BSIPs, second step is to make UI compatible to the changes / new features of core 4.0
25
Stakeholder Proposals / Re: [Worker Proposal] Bitshares UI, 2020 (6 months)
« on: May 26, 2020, 09:09:37 pm »Any estimates how much it would cost to just get the most urgent done ?
Depends how you define urgent. Node connectivity seems to be a prominent issue.
26
General Discussion / Re: Question about a problem depositing BTS from a exchange wallet.
« on: May 08, 2020, 05:40:06 am »
The external exchange should have a withdraw BTS option, and hopefully documentation with it.
Normally, the process is: you First, if you don't have one, create your own BitShares account. Second, you withdraw using the account name as withdraw destination.
Normally, the process is: you First, if you don't have one, create your own BitShares account. Second, you withdraw using the account name as withdraw destination.
27
Technical Support / Re: Change fee schedule using wallet cli
« on: May 05, 2020, 03:58:20 am »
committee proposals have mandatory review period, thus this proposal will only execute at expiration date and if all approvals are peesent
28
General Discussion / Re: How to send blind transactions?
« on: April 27, 2020, 04:47:10 am »Is there a way to send blind transactions?
Where is the implementation of TITAN?QuoteWith TITAN (Transfer Invisibly to Any Name) we have provided one layer of protection: generating a unique address for every transfer. Unlike Bitcoin, BitShares uses named accounts which makes it easier to remember and share your account name. TITAN only keeps your transaction history private, with no link to your account name, to 3rd parties. The parties to the transaction know the balance address and account name are linked. - Bytemaster's blog 12/23/2014
Blind transfers are possible, not implemented in UI. I think DEEX had an implementation.
29
Stakeholder Proposals / Re: Proxy:B-DEX
« on: April 07, 2020, 01:27:46 pm »Discussion between another Dev and Abit about paying 2 times for the same audit on the core prelude worker
$75/h to abit and later for the same work 3% of all funding to bbf
You may call both "audit", but the actual tasks are fundamentally different. Happy to elaborate if interested.
30
Stakeholder Proposals / Re: [Worker Proposal] Bitshares UI, 2020 (6 months)
« on: April 07, 2020, 07:07:54 am »
Complaints on white screen issue seem to be increasing, tied to greater number of offline nodes.
Maintenance would be needed urgently
Maintenance would be needed urgently
