Massive work done this week:
https://github.com/kenCode-de?tab=repositories I would *highly* recommend you play nice with **ALL** of your shareholders
because you will need their votes for a hard fork
... I can not approve a hard fork.
@xeroc -threatening us with your Proxy-power because I do not "play nice" is not productive at all. We *greatly appreciate* the python that you write. You are not a Core Dev though. Fyi, the
20 other hardforks in the queue will need to be properly audited:
https://github.com/bitshares/bitshares-core/issues?q=is%3Aopen+is%3Aissue+label%3Ahardfork You are not qualified to do deep-dive security audits.
Advising people that their money is safe with the existing "confidential transactions" code, and, giving people security advice is probably not in your best interests.
Speaking of security, since you did not finish the Trezor integration, I would be more than happy to acquire that project from you as well. As usual, a security audit will be done on it, so please advise to the locations of the work that you did so that we can get it completed.
I don't believe you have explained that yet, and if I'm wrong and have overlooked that higher level plan you have in mind then just point that out.
@Thom -I will tell you when you can start your Stealth marketing campaign once the public has had a few months to fully test and security audit it with us (not just Stealth, but the encrypted C-IPFS backups as well). I do thank you for your efforts, and would love it if you organized the marketing campaign for Bitshares' Stealth.
In the world of software, never give out dates (right Stan?
). I learned that lesson 30 years ago. Obviously though Thom, I took your comments very personal, so I sincerely apologize for my knee-jerk reaction. I am building things that have never been built before, so it's a bit tough to even hand out any timelines. I am well aware of what needs to be done, nobody has ever had to ask me for updates, and I do my best to detail our roadmap and progress right here on this lovely forum every week, so nothing more.
BlockPay related: "Direct DEx" is 99% done and has been merged into our new graphenej repo here:
https://github.com/kenCode-de/graphenej This week we are:
- Upgrading the Bridge code
- Transactions interoperability with graphenej
- Redesigning the eReceipts a bit so that all devices can display them properly
- Starting the initial wireframe drawings for the new UI/UX and 1-Step Setup
Alfredo Garcia monster updates this week: 1) "Boost libraries could not be found"
https://github.com/bitshares/bitshares-core/issues/251 Working on this issue led to bitshares-core compilation in windows.
3 possible methods: - visual studio. - cygwin. -mingw.
Goal is to make it work locally and then update or create new documentation page for building it in windows:
https://github.com/bitshares/bitshares-core/wiki/BUILD_WIN32 2) Working on a new updated version of market_history plugin. Working in a new version based on the Steem plugin.
Will be ready for testing over the coming days.
3) Resolving Issue 231:
Websocket “spamming too much data” issue
Working on last proposal from Vikram to use a separate file for some changes to don’t break design.
https://github.com/bitshares/bitshares-core/pull/245#issuecomment-286267666 No spam sub function
https://github.com/bitshares/bitshares-core/pull/234 closed
No spam sub function
https://github.com/bitshares/bitshares-core/pull/249 merged
https://github.com/cryptonomex/graphene/issues/540 closed; moved to issue 231..
Resolving it tonight (Fri the 31st) most likely:
https://github.com/bitshares/bitshares-core/issues/231 4) Fixed the get_ticker segfault
5) Assist the Stealth Team with the new api, providing documentation and guidance with hooks in the UI.
6) Working on this week:
Verify that public websocket API does not expose sensitive API calls
https://github.com/bitshares/bitshares-core/issues/33 Tackling more Bitshares Core Issues:
https://github.com/bitshares/bitshares-core/issues?q=is%3Aissue+is%3Aopen+sort%3Acreated-asc Bitshares StressTest Looking into why nobody could break through the ~3300tps barrier.
-------
Bitshares PenTest As you guys know, I take security very seriously (#tinfoilken). I would like to hack on our Witness and full-node operators next. To do so, I will hire an outside Firm which specializes in security auditing and penetration testing. This will require funds from the pool. I am researching the options now, finalizing the formal Proposal, and will post their Bid here as soon as possible.
-------
Smartcoins Wallet: I might release one more 1.x version of the Smartcoins Wallet on google play, but work has already begun on 2.0.
"Carbon" (Smartcoins Wallet 2.0) features:
- Carbon natively supports 6 blockchains (Bitshares, Bitcoin, Dash, Dogecoin, Litecoin and Steem).
- Carbon supports HD Contacts (rotating addresses) and Contacts Groups (for paying multiple people at once).
- Carbon allows you to pay at any BlockPay merchant with just 2 taps (scan and approve the payment).
- Carbon supports both NFC tap and pay, as well as v10 QR Codes.
- Carbon supports eReceipts from BlockPay merchants.
- Carbon supports Loyalty Points from BlockPay merchants.
- Carbon supports Recurring and Scheduled Payments to one, or groups of Contacts.
- Carbon supports "PIN, Pattern, or Pocket" Security (draw patterns and yubikey neo (NFC/U2F)).
- Carbon supports Overdraft Protection (ie: allows you to "cash out" a backup asset to cover your grocery bill).
- Carbon supports automated encrypted backups to C-IPFS.
- Carbon uses C-IPFS as its App Store (no more Apple or Google "approval" needed).
- Carbon cannot be censored or blocked.
- Carbon is a true Dapp, completely decentralized App architecture with C-IPFS.
- Carbon supports coin shifting (bridges one coin into another).
- Carbon supports Key Dump (allows you to change out your private keys if your wallet is stolen).
- Carbon supports 44 languages.
- Carbon uses the Bitshares blockchain for fully-confirmed transactions in 3 seconds or less.
- Carbon allows you to easily share your coin addresses and Contact info via QR Code, SMS, Telegram, etc.
- Carbon supports Transaction searching, filtering and exporting to PDF and CSV formats (for your Accounting).
- Carbon is 100% free and will be open sourced on Github.
- Carbon can be white-labeled with your own logo, color themes, etc...
Some initial mockups we're working on:
The animation work began yesterday and will probably take a couple of weeks. Once that is complete, I will post a video of it here. Then, coding the new UI/UX will take a few weeks as well. While the Carbon UI/UX is being coded, the new UI/UX for BlockPay will begin. It will follow my agenda for a 1-Step Setup (not sure if we can achieve that with so many features in the software, but I'm sure gonna try).
Here are the high-resolution image mockups if you guys want to start marketing Carbon over the coming days and weeks.
https://drive.google.com/open?id=0B-LdNgnj_1qyUTNPNGI2b2lQcDQ If anyone is wondering WHEN Carbon will be released, then just give them a link to this forum thread. As usual, I will post as much as I can, when I can.