To me it looks like they are buying BTS with USDT and liquidating it for BITCNY

You can't forbid people to trade. If exchange ZB.com has USDT volume to trade you can't stop them. It's "business on top of the blockchain" with no limits or terms of agreement, so just buckle up and pray.

Local bureaucracy with Committee members and rest should anticipate this and prevent, instead of alerting now when already millions are gone through BTS and Tether.

We would like to create a page/link (locked by password), to provide detailed specs about each and every RPC Bitshares node running world wide.

Each and every faucet are showing different nodes. There is no available real list or statuses on owner of them, availability or what they are actually running.

More and more users are, more and more often, facing Transaction Broadcast Error, Failed to Confirm, etc. As soon as the node list is being swiped by user (which should be not doing ti manually and many of them don't even understand where and what is the problem), and one normal Node is found, it's all good and working.

There is something seriously wrong with infrastructure, and since recently there was proposal about Load Balancers and making Bitshares network more stable, can we first get an info on where are we at this moment ?

Requirement:

1.) All owners of the nodes running official Bitshares, please deliver details in order to populate the page and list.

-Location
-IP (RPC only)
-RPC port
-Domain Name (RPC only)
-Server Configuration
-OS/Firewall Configuration (OS, services running such as Nginx, redis, mysql and their versions, ports, security details - fail2ban, csf/lfd...)
-Bandwidth Test
-Docker or Source

ETA:

- 3 Business Days to do Stress Tests by sending/simulating a lot of requests to each node.
- 6 Business Days to do Ethical Penetration Tests on all nodes.
- 1 Business Days to deliver the page url with the dataaccess visible to selected members of Bitshares Community, so we can track all decentralized individual servers are that are representing Bitshares, getting more knowledge and data where the actual problems are.
- 2 Business Days to provide Full Reports on results of Availability/Penetration testing.

When we are well aware of the STATE OF THE NETWORK itself, we can support more.

There is no cost for this, just reason, logic and focus from the community is needed.

Many thanks

Bitshares Thailand

on behalf of
@apasia.tech

Dear Digital Lucifer, I'm glad to see your activity and so loud words. The whole system will be happy when you will deliver any quality solution or even product on BitShares network.

The main idea of the poll and topic is preparation before creating RnD workgroup and getting feedback from community, about wishes and needs. Any specific plan or project will appear only in the end of 2nd stage, as well as team of experienced developers will be combined in the team and announced. It's not a wise approach to start development, before goals and aims are clear to all parties. Listed ideas were created not only because "it would be cool to have this on BitShares", but also, because we have 2 teams (business analytics and developers) agreed, that in the end, solutions like these are technically possible and demanded. They will never seem easy and so obvious, as presented, so it's not surprise for me, that your reaction is negative mostly.
I'm also not a forum-speaker and don't see sense in debating right now, before we've spent time on researching and tried prototyping. I believe, that you're experienced enough and can bring a lot of profit in ecosystem, so will look attentively on your development process and github account, for possible useful learning.

Ivan,

Appreciate your very strategic and well crafted answer. You seem to have a very well speaking/communicating skills for a non forum-speaker, but i do agree with you we are not here to debate. My github account is more private since all our projects are being handled with Asana and Slack.

I would really appreciated if you would add me in Telegram by using number from signature.

Cheers,

Luci.

I would add another one:
* testnet.bitshares.eu runs version 160106 of UI, upgrade to something newer

Tim (STokens) had that one on the list as well, but since even the master branch for mainnet is downloading old one, i didn't want to place it there for now

He also added Windows solutions for core, ui and wallet. There has been some testing on Windows Server stations. Will update soon.

Anyway, awesome comment and addition, anyway.

Thanks,

Luci

Bitshares community,

Wish you all good morning from Thailand!

Since earlier I've read something from @intelliguy very nicely written, yeah this is DEX and until someone step up, there will be no project management.

Today was perfect morning for me, in the Bitshares DEX channel. I had very nice opportunity to communicate on some issues and needed fixes with CTO of STokens. As CTO to a CTO of 2 crypto-involved entities, I'm sure there is no need for anyone to question the integrity of our knowledge and further post content.

Now, let's imagine that i'm investor or a shareholder, with a secret profile and nobody knows who I am. I'm coming here to test my investment/project im staking in, and i would like to see how fast developers and other shareholders will reply to these issues:

● [FUNNY BUG] Number of coins given by the faucet should be higher than 10,000. 10,000 as start is completely worthless against 10,000 coins Life-Time member fee, or 5,000 fee for issuing new asset.
● [FUNNY BUG] Lower the vesting period from 365 days to something more reasonable - It's just a TESTNET.
● [FUNNY BUG] When creating an MPA from the GUI, the field for minimum number of price feeds does not recognize any value but the original as an integer. The only way to currently create an MPA with a higher or lower number of price feeds is:
     ○ Creating it with a full node, witness or cli.
     ○ Updating the minimum total post-creation.
●  [DOCS] Updated tutorials for interacting with the testnet from one of the many python tools for Bitshares. That could be graphenelib or pybitshares, even though pybitshares has the best documentation, just needs updating.

Testnet is not only for Bitshares Devs, but for partnering companies, business on top of it, gateway developers, 3rd party platforms that would like to integrate with, etc. It has the same importance as the real node (mainnet)

Would love to see some comments and ETA's on this

Many thanks,

Lucifer.

Thanks for the tutorial. I'll try and let you know in the next few weeks.

You are most welcome, i feel better already seeing that you are not under pressure anymore. Take your time, i'm around.

Cheers,

Luci

Quote from: Digital Lucifer on October 30, 2017, 04:35:54 pm

So, if anyone has one, i'm happy to comment in the future, white papers, nice diagrams, charts, whatever is ok for a marketing event, not for any serious development. I'm sure most will agree on this.

Since there are more users, and investors, using Bitshares than there are developers, there is always a wide divide of people who have opinions, suggestions, and complaints.

Right about now is when the appreciation of the teams Bytemaster use to lead developing Bitshares is missed.

It's like the system is on autopilot (development wise) and only now are people raising important questions about how the system works, where trust lies, how much trust is "too much trust" and now a recent discussion about NDA's among proxy witnesses has been raised.

This is all very long overdue, and I'm happy to see it.

There is a lot of interested money in this platform (always has been), so financing our future is going to be quite easy.

But when you say:

Quote from: Digital Lucifer on October 30, 2017, 04:35:54 pm

I seriously have to stop answering and stop talking completely. There is so much going on, and currently how it's being presented is just a talk, even from my side.

You are incorrect.

It's not "just a talk".  It's a united level of understanding, that is really important going forward.

Quote from: Digital Lucifer on October 30, 2017, 04:35:54 pm

Deliver that as proposal even with a broken monkey in the box, and i'm sure that any serious businessman related to this network will push the proposal through.

I'd rather not see lots of proposals with a broken monkey in the box.  That just leads to confusion, frustration, and can camouflage real decent proposals if they are hidden among all the other broken and non-possible proposals.

I hear your frustration, but removing talk in the favor of creating broken monkey in the box proposals is not a better solution.

I agree on 100% of what you've said, but i have to clear up few things that you got wrong about my words.

1.) "I seriously have to stop answering and stop talking completely. There is so much going on, and currently how it's being presented is just a talk, even from my side. " - I'm lead developer in my company and CTO in another IT company that Ross owns for 4 years. 4 years even having my own company never moved me away from the development. Having Ross as a business partner lets me be out of management even for my own company so i can dedicate my real skills to contribution for our business, where everybody are doing what they are most skilled to do. I've been slapping myself in that sentence over the wrists, by talking to much, delivering to little, so i want to back off to development, coming back here with results and real proposals, not just talk, because we do have healthy and realistic concept and ideas in progress not going over limits of ourselves. Spending my time here for talk is taking time from project management and coding/engineering which i personally enjoy to do.

2.) "Deliver that as proposal even with a broken monkey in the box, and i'm sure that any serious businessman related to this network will push the proposal through." - EVEN if you have broken monkey with knowing exactly whats broken about it, knowing how to fix it or proposing possible fixes with prices and estimates on it, and doing estimate on an each fix, you are being professional as Mitsubishi Factory in Japan. It's matter of personal opinion, and as i said you are completely right 100% about all what you've said, but i prefer rather visible broken monkey that can be tested, rather than paper that is saying that monkey will run in a golden box, but i cant see monkey or a box. Developers proposal needs to based on a demo of the work for project/proposal being made. At least outside of Bitshares world, like in regular B2B circumstances. I'm strong believer that Bitshares can sort out roadmap it has with a lot more performance if developers put a bit more effort in project management.

Since it comes from a developer, i think its rather rational thing to say

Cheers, and i really agree with you and understand fully your perspective on it. It's just small difference of an opinions how things to be done.

Luci

Quote from: mostar on October 30, 2017, 08:21:55 am

https://crypto-bridge.org/
Calim they solve the counterparty risk by implementing decentralized gateway to bitshares DEX !?

Is't it the same as idea 4:
Creation of Trustless (Decentralized) BTC gateway for DEX.

What do you think?

It is not clear to me. It looks like a Federation of Gateways, distributing the risk of third parties. But in the end uses IOU (UIA) as Open Ledger.

(BTC is BRIGGE.BTC)

What is a Gateway?

A gateway is a service that you can use deposit/withdraw coins and that converts coins to proxy-assets (UIA). Each issued proxy-asset is backed 1:1 with the real coins by the gateway.

If someone has used it and has another opinion, say so.

I agree with definition what is a crypto gateway, even though fiat gateway is completely another story.

I seriously have to stop answering and stop talking completely. There is so much going on, and currently how it's being presented is just a talk, even from my side. The fact is, develop test monkey in a box, collect all bugs you can, do estimate on bugs/missing things/fixes in days and possible solutions with hours, whoever you are. Deliver that as proposal even with a broken monkey in the box, and i'm sure that any serious businessman related to this network will push the proposal through. That proposal have a goals, targets, limits, collateral. It's not just developers estimate, its project/product management with SLA on top of it and there is no flaws in the process, with maximum burn time (additional) can be 10-12% of total amount proposed and that always pre-calculated in original proposal as collateral damage.

So, if anyone has one, i'm happy to comment in the future, white papers, nice diagrams, charts, whatever is ok for a marketing event, not for any serious development. I'm sure most will agree on this.

Cheers,

Luci