Author Topic: [ANN] BlockPay -Your favorite store can now accept any crypto thanx to Bitshares  (Read 67305 times)

0 Members and 1 Guest are viewing this topic.

Offline kenCode

  • Hero Member
  • *****
  • Posts: 2283
    • View Profile
    • Agorise
Looks interesting .. seems to be quite some process you are making..
..
I still haven't understood what you guys are working on with STEALTH on the backend. Could you please provide us with some sort of specifications? You'll need to provide those anyways if you need a hard fork

As I learn more, I will keep posting it here. Alfredo is helping gordon and alex a bit now too, so we are moving on Stealth as fast as we can. Hopefully no additional hard fork will be needed for Stealth, but if one is needed, we will most likely roll it in with these others:
https://github.com/bitshares/bitshares-core/issues?q=is%3Aopen+is%3Aissue+label%3Ahardfork
kenCode - Decentraliser @ Agorise
Matrix/Keybase/Hive/Commun/Github: @Agorise
www.PalmPay.chat

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12920
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Looks interesting .. seems to be quite some process you are making..

Quote
So far performance has been good, sending to a Stealth address from public address (cli-wallet), but if it were to become an issue we are already looking at moving that processing to the server along with async. As this progresses I'll keep you guys informed right here on the forum. So far so good though and you guys should be able to join us on our testnet in a few weeks too, at least for the basic stuff. The UI will probably need refinements as always.
I still haven't understood what you guys are working on with STEALTH on the backend. Could you please provide us with some sort of specifications? You'll need to provide those anyways if you need a hard fork

Offline kenCode

  • Hero Member
  • *****
  • Posts: 2283
    • View Profile
    • Agorise
Impressive as always kencode!

+5% +5% +5%

Thank you guys :)
 
Tons of updates this week!
https://github.com/kenCode-de?tab=repositories
 
BlockPay related:
 
Graphenej (https://github.com/kenCode-de/graphenej): After having partially implemented the limit_order_create_operation, some issues were still present and transactions with the new operation were being rejected by the network on a missing authority error. This usually means a discrepancy between binary serialization used to generate the signature and the provided JSON-formatted string describing the transaction itself.

A couple of errors were found and fixed, which finally made the transactions bearing that operation to be accepted by the network. This commit also introduces a simple test suite for the transaction using this operation as well as minor adjustments to the test of the operation itself. See:
https://github.com/kenCode-de/graphenej/commit/a9a550491b4a0b4b3cd76b6c8a21f1d4fa8e7b13
 
Support for the limit_order_cancel_operation was introduced, which also features the corresponding test cases. See:
https://github.com/kenCode-de/graphenej/commit/aa642edce9188185a68695e196244291beb88dc5
 
Finally, some changes were made to the library in order to make it more easily available for everyone via the maven central repository. This will allow us to seamlessly work with updated versions of the library on multiple projects, by using semantically versioned releases of it. This was required since it was starting to become a hassle to keep the library updated on multiple projects and to manually port the updates coming in from some of my other Devs. See:
https://github.com/kenCode-de/graphenej/commit/c6e4b9ea5b070c8629563e528b4189a376f31ea2
https://github.com/kenCode-de/graphenej/commit/425cb663b1dad8a5c59ad28cf521955a36f1ddda
 
The result is that our library can now be included in any android project by just dropping these lines in the corresponding build.gradle file:
 
Code: [Select]

dependencies {
    compile 'com.github.kenCode-de:graphenej:0.4.1'
}

The graphenej library was removed from BlockPay itself and just referenced now like described above. Work has now begun in making use of the 2 additional supported operations that will give us "direct DEx" access and avoid having to use the Bridge services twice for some asset pairs. Speed is everything when standing at the cash register, right? See:
https://github.com/kenCode-de/blockpay-s/commit/8c429fe4c7edd55d76fe409140760fd588796174
 
C-IPFS related:
 
This week, we worked on a simple node transfer protocol to allow for easy and wicked fast transfer of files and data, without the overhead of a larger protocol.
 
We have in place a test that is running the code through a complete startup, connect to the "swarm", ask for an existing file, have the swarm determine the best peer(s) to serve the file, connect to the appropriate peer(s), and retrieve the file. We're currently on the "find the best peer" part. And I am confident that once that is in place, the rest of the test will work fine and will be up and running by tonight (Friday).
 
DSHT (Distributed Sloppy Hash Table), or "Coral" as it is also known, is being worked on this week too which will radically speed up response times (our way of sneaky "load balancing" (self-organizing clusters) if you will). Speed is everything when you want to access your files, latest BlockPay apk and app assets, etc. Who needs app stores when there are thousands of peers willing to serve it up for you without microsoft, apple or google's "approval".. aaaanyway.. i tip my tinfoil hat to them for trying. #tinfoilken
 
Development of NodeIO Protocol:
https://github.com/kenCode-de/c-libp2p/commit/69cbff9cd6173177a4b403f9776a3261d3b758d6
https://github.com/kenCode-de/c-libp2p/commit/b6a94c7c11831398e06597f4c804b65ce2b7d885
https://github.com/kenCode-de/c-libp2p/commit/0d0c9bde535062cf8baf175b4c4d84e5b60af1bc
https://github.com/kenCode-de/c-ipfs/commit/e8b8d06f24e6b1275053ce594af9ef208b023b38
https://github.com/kenCode-de/c-ipfs/commit/0b238eb5ace2d7d19f4360949c94fb518e7289ff
https://github.com/kenCode-de/c-ipfs/commit/cfcabaecd0a25f815f9cc1f5095edf9f52b094c7
 
Compiler changes for CentOS and more extensive tests, plus general code efficiency, cleanup and testing:
https://github.com/kenCode-de/c-libp2p/commit/9776ff15a091507ceb95ccf41c01d09282ae24f8
https://github.com/kenCode-de/c-libp2p/commit/bd9f219b504747c461bc01ae07d17858ebfaa2bd
https://github.com/kenCode-de/c-libp2p/commit/41ef0e54929d8184a808e152b41542f889f5a2f1
https://github.com/kenCode-de/c-ipfs/commit/8edc94509c54e4851d2f929b0e65f6a4ee9530d0
https://github.com/kenCode-de/c-ipfs/commit/83242b0046d2d0b1bba84dbfe698014812a96141
https://github.com/kenCode-de/c-ipfs/commit/618264c70962d17c9f7e4dc7287ac28ea1a825da
https://github.com/kenCode-de/c-ipfs/commit/25a2fa0c65934a66aac39d0dd3a0de2e20149dd2
https://github.com/kenCode-de/c-ipfs/commit/640e4be5be23bf7579cd613999d6bfc95e9ca366
https://github.com/kenCode-de/c-ipfs/commit/d25e088b7c5427fa565b9e299fb268e5c9b2e881
https://github.com/kenCode-de/c-ipfs/commit/6c64b55176e43fe6eb9ff7cbce893620f8a1b49d
 
Plans for the coming week:
 
We'll continue to work on the "swarm" features, as well as replication. We'll also look into the modifications the Go-IPFS has done for security and performance improvements of the dht/kademlia standards. Some work is being done to decentralize our access to the Bridge too, so that any server downtime could be handled gracefully. We don't want thousands of merchants unable to process customers because a damn third party's server went down.
 
Android Smartcoins Wallet:
 
It's nice having WIF key support now! Minor improvements were made to it this week, where we changed the double account verification logic, just in case it is a WIF based backup bin file to a method which is now calculating and comparing both (vs brainkey derived) and if they differ, assume it is WIF key backup, and avoid double checking at the network. In other words, it operates more efficiently now, is a bit "smarter", and uses less bandwidth overall.
 
We fixed a memory leak that happens because of an unexpected (yes or cancel) dialog box. Removed it since it's no longer needed anyway.
 
We switched from TZ to LZMA for compressed files (some parts of the code were still using deprecated code from cryptonomex/graphene lib).
 
As you know, we are doing a lot of work on the Transactions and eReceipts code for BlockPay and the Smartcoins Wallet, some pretty major refactoring goin on now so it is nice and clean and operates seamlessly with our new graphenej lib too.
 
Related commits:
 
f549316cbc1db4d3820ea6f29c3b483890c9de73
341eff49d609854ef7e5dfbd009b0988a5c51f0b
a5cac8de7819132ecadc6b8d0cd8b0591297034b
a8080a05951b385826118cfd902ace2ddf500a71
07180e4327c2d909f7edf787bd851029a224b40f
4d256ab620cda5b9dd68861edb97312d0eb6021e
 
Once the Transactions and eReceipts code has been finished and thoroughly tested then I will publish an update to google play, probably in the next week or so since I am including a bunch of other cool stuff we have been working on..
 
Since Smartcoins Wallet 2.0 (codename: "Carbon") will natively support 6 chains, here is some of the work that was completed this week on that:
  • Added a separate button to send a receive to each coin
  • Change the transaction history to display the bitcoin and altcoin transactions
  • Make eReceipts work and show which coin you sent/received etc
  • Testing several issues showing Balances
  • Implementing Litecoin and Dogecoin logic, testing without server
  • Researching Dash InstantSend, running first tests
We have all the logic to make the altcoins work, the only problem now is the server software for their chains..
 
Dogecoin seems to be the most difficult because of the lack of support, their last update was 2 years ago. For Litecoin this week we have the news that they updated their library, so that just leaves Dogecoin.
 
Lots of server tests too just to make sure their libs don't have any leaks etc. I want these integrations to be as maintenance-free as possible.
 
For the InstantSend feature for Dash, we have run several tests, and had found that feature on server side, and dug into their libs and found this: Now we just need to set the servers up for this, change a couple of files on the server (they're all nodejs so no worries), and only affects the Dash libraries. Easy-peasy.
 
The tasks for this coming week are:
  • Editing a couple of Dash files on the server to support InstantSend
  • Change the Contact screen a bit to support Bitshares and altcoin Contacts
  • Change the Send screen so that you can send any of the coins or altcoins that you own
  • Merge the develop branch into the main branch
  • Begin R&D for the native support of the Steem chain

Stealth related:
 
Lots of work being done on the new Stealth api so that we can use it in the web wallet, light client wallets and eventually all mobile devices.
 
More commits:
https://github.com/kenCode-de/bitshares-core/commit/a74639131e0812e2664329037af8b1f7d87daa60
https://github.com/kenCode-de/bitshares-core/commit/6ff204d6f329c14154598997b6f23b37711f5d41
 
Stealth commands are being ported to javascript too for the UI. As the api grows, so does the UI actual functionality.
 
So far performance has been good, sending to a Stealth address from public address (cli-wallet), but if it were to become an issue we are already looking at moving that processing to the server along with async. As this progresses I'll keep you guys informed right here on the forum. So far so good though and you guys should be able to join us on our testnet in a few weeks too, at least for the basic stuff. The UI will probably need refinements as always.
 
Alfredo Garcia, Bitshares Core Dev update:
 
Alfredo as always is kickin butt too, here is some of his work from the past week:
1) "Clean up re-indexing logic"
https://github.com/bitshares/bitshares-core/issues/175
Tested, commented and requested to close.
 
2) "Fix the get_ticker crash"
https://github.com/bitshares/bitshares-core/pull/250
There was a segmentation fault in the get_ticker function. Researched. Fixed (found another issue and we're working on that one now too).
Awaiting approval and merge on this one now.
 
3) Closed github issues: 4) Got this one closed:
"cli_wallet: create_account_with_brain_key doesn't save owner key"
https://github.com/bitshares/bitshares-core/issues/196
 
5) Requested to close - Closed by TheTaconator with fix..
"Proposed fix for Issue #196: create_account_with_brain_key doesn't save owner key"
https://github.com/bitshares/bitshares-core/pull/235
 
6) Configured and started using our BitShares Munich testnet server for development environment
 
7) Helping out Alex a bit on the Stealth UI and getting all the json involved in the blinded and Stealth transactions.
This should be completed by this sunday the 26th.
 
==============
On a side note, I'd like to ask the community if I can add one more of my Devs to help out Alfredo. If it's cool with you then I will have Chris write up the 6mo Worker Proposal and get it posted asap for your review so we can get him voted in. It's time we ramped things up even more imo.
kenCode - Decentraliser @ Agorise
Matrix/Keybase/Hive/Commun/Github: @Agorise
www.PalmPay.chat


Offline cusknee

  • Full Member
  • ***
  • Posts: 174
    • View Profile
  • BitShares: cusknee

Offline kenCode

  • Hero Member
  • *****
  • Posts: 2283
    • View Profile
    • Agorise
Tons of updates this week!
https://github.com/kenCode-de?tab=repositories
 

 
BlockPay related:
 
Lots of work being done on the Settings screen this week and next. My goal is to have a 1-step setup. I'll upload some more this coming week so you guys can have a look but for right now the code is a mess while everything on that screen is being reorganized.
 
Another major thing that I am cleaning up is the way transactions and eReceipts are displayed. This will be updated this week as well and then I will get you guys another version release published on google play, probably on thursday or friday.
 
C-IPFS related:
 
Final cleanup being done now, efficiency improvements in the code, and also adding support for Coral, Bitswap and Cjdns. With the completion of C-IPFS, at least to the point where it is perfected for our needs, this allows us to begin the 2.0 Core for BlockPay and Carbon (the rebrand of the Smartcoins Wallet for v2.0).
 
Related commits:
https://github.com/kenCode-de/c-libp2p/commit/17dfadb6fd1f4032dcc439a19cb24dd337b96b4b
https://github.com/kenCode-de/c-libp2p/commit/52f8ce2b3dd96868785413a60c6dc687e4e8232f
https://github.com/kenCode-de/c-libp2p/commit/f0bb7375c39d1d0d951ca490a2a2520a945f43be
https://github.com/kenCode-de/c-libp2p/commit/8463e0b06b0943a7dbba9972f1cd036af844e1fd
 
Android Smartcoins Wallet:
 
Adding native support for 6 chains is not easy. Native Dash support and InstantSend is in progress now and into next week. This means we are almost done with 5 of the chains already. Just another couple weeks and they will be ready for our v1.7 release. Work finished this week:
  • Fix logged UI logic OR in imported account
  • Add Support for WIF Imported Account
  • Fix UI Problem with Upgrade account button in Settings
  • Export Bin for WIF Imported Account
  • Import backup bin logic for WIF only based accounts
  • Partial fix for instant update for Transaction
Related commits:
https://github.com/kenCode-de/smartcoins-wallet/commit/15fac5ac9e442d35118f23b8df66e704fb1ab39c
https://github.com/kenCode-de/smartcoins-wallet/commit/6c7ff95fdc28ccf75f79db72ad5c1c46e351abe1
https://github.com/kenCode-de/smartcoins-wallet/commit/c70b342962449be09b273b9852bb8985c1fb35f2
https://github.com/kenCode-de/smartcoins-wallet/commit/abc866528c5977655a28c0f81c44a8267542ecff
https://github.com/kenCode-de/smartcoins-wallet/commit/45c6ad95f5e10b31631e45bf216e8b07936c7bec
https://github.com/kenCode-de/smartcoins-wallet/commit/a66863e4c8825a1e518191c03eecc159bc5f4bbe
https://github.com/kenCode-de/smartcoins-wallet/commit/67e240802f828a82a231413a0309a67460726362
https://github.com/kenCode-de/smartcoins-wallet/commit/d0d921bf2b7eb4c5aa4889c7ec549f2fb317b5d7
https://github.com/kenCode-de/smartcoins-wallet/commit/ec5e124428907bf49bd0bfb9624c27eefd2a4404
https://github.com/kenCode-de/smartcoins-wallet/commit/7426d7014295a14bba587c145ec5db4e9c5be134
 
Details:
  • Testing Dash masternode api
  • Implement the Dash api library (Java)
  • Implement Dash coin logic
  • Changed the Balances screen to work with all coins
  • Add Dash Manager
  • Implemented Dogecoin and Litecoin networks into the java library
The masternodes server and other full nodes are running great, no problems so far. Network parameters are set. For Dash, we are using this lib as our main reference point:
https://github.com/HashEngineering/dashj
 
Now that we have full, native Dash support in Carbon (Smartcoins Wallet 2.0), the only feature that needs to be finished up and thoroughly tested now is the InstantSend feature.
 
For the native Litecoin and Dogecoin support... We've had to change several things in the UI, but if we keep moving at this pace then we should be able to merge the develop branch in the next week for final testing (assuming the Dash InstantSend feature goes smoothly).
 
With these tasks finished, it looks like we'll be finishing 1 week ahead of schedule. Then, just two things left:
  • The Equivalent Value feature: This is the small fiat value that shows underneath of each of your crypto balances.
  • Contact sharing: This is done more or less but we have not had a chance to fully test it yet
Stealth related:
 
The new api is coming along nicely. No problems encountered, no bugs, no memory leaks or any problems communicating with the core. Seamless. This is week 3 of 6 for the api, and as each new function is built, the UI connections are being hooked in and tested. The 3-way switch too. Man I'm glad I thought of that as there was no easy way earlier to give the user so many options. We'll never get mass adoption if grandma can't use it.
 
Additional Stealth API related work: In the UI, we're OOP'ing both Stealth, and the Blinded transfers for ease of future use, and use by our mobile and Integrated BlockPay installs {Contacts-Accounts-Database-Transfer}. We also prepared the modes functions for future tri-state (Normal, Blinded, Stealth (3-way switch)) transactions {for Account creation & transfer screens}.
 
Alfredo Garcia, Bitshares Core Dev update: 
 
Failed is_valid for address in get_account_history
https://github.com/bitshares/bitshares-core/issues/159 closed
 
issue “Throw / catch specific exception in db.close()”
https://github.com/bitshares/bitshares-core/issues/81
pull request: https://github.com/bitshares/bitshares-core/pull/246 closed
 
Why is bitcoin being exported with the bin file backups? see the second code chunk nelson posted:
https://bitsharestalk.org/index.php/topic,23798.msg302837.html#msg302837
@sigve Deposit keys are just addresses for withdrawal of OPEN.X assets, blocktrades has made use of the database to store them. DONE.
 
Need ability to poll for all holders of an asset
https://github.com/bitshares/bitshares-core/issues/107 closed
 
issue: “Get rid of fc::time_point::now()”
https://github.com/bitshares/bitshares-core/issues/76 closed
pull request: https://github.com/bitshares/bitshares-core/pull/247
 
Remove NTP time
Vikram didn't merge Alfredo’s exactly, but used it to merge another one here:
https://github.com/bitshares/bitshares-core/commit/8ae1f6b3a52c36b0c9c454654a338511c0f4812b
 
Lots of contributions to the BitShares StressTest; servers, code, consulting with other sysadmins, etc.
Preparing for the next stress test, evaluating p2p code now to make the next stress test blow through that 3300tps barrier.
kenCode - Decentraliser @ Agorise
Matrix/Keybase/Hive/Commun/Github: @Agorise
www.PalmPay.chat

Offline kenCode

  • Hero Member
  • *****
  • Posts: 2283
    • View Profile
    • Agorise
In China , we cant visit in google.
Why not add apk in https://github.com/kenCode-de/smartcoins-wallet/releases

Feel free to build it from src yourself, or download the Smartcoins Wallet from aptoide, yandex, alternativeto, slideme or f-droid (they should have it live by now).
If you meant the BlockPay apk, I really don't want to post the src for that just yet and give the competition an edge, at least not until it gets some traction first.
 
edit: belay my last on those alternative app stores. apparently, they disapprove any apps that include crashlytics. i want to keep crashlytics in our apps for just a couple more weeks until there are no more crashes reported. it helps us to more accurately determine the cause of the devices that crash (make, model, os version and so on).
« Last Edit: March 14, 2017, 03:15:23 pm by kenCode »
kenCode - Decentraliser @ Agorise
Matrix/Keybase/Hive/Commun/Github: @Agorise
www.PalmPay.chat

Offline ebit

  • Committee member
  • Hero Member
  • *
  • Posts: 1854
    • View Profile
  • BitShares: ebit
« Last Edit: March 11, 2017, 01:50:17 pm by ebit »
telegram:ebit521
https://weibo.com/ebiter

Offline kenCode

  • Hero Member
  • *****
  • Posts: 2283
    • View Profile
    • Agorise
Thanks for all the hard work @kenCode, Christoph, and the whole blockpay team.

+5% +5% +5%

well done +5% +5% +5%

Awesome update kenCode.

@kenCode Are -- are you a machine?? :o

Yes, I think he is a machine :)
Well done my friend, awesome report!

+5% +5% +5% +5% +5%

Thank you guys :)
 
BlockPay v1.5.9 released. In this version we cleaned up the settings screen quite a bit, removed more of the redundant stuff that just annoyed people. At the end of this coming week we will start cleaning up the Blocktrades screen too so that it is easier to get the app setup initially. Lots of cpu/mem/bandwidth and speed improvements in this release. Known issue: Transactions screen is disabled for now and still needs to be upgraded to our new graphenej library and it looks like hell imo.
 
https://play.google.com/store/apps/details?id=de.bitsharesmunich.blockpay
 
ps: i hate to ask, but if you haven't done so already, can you please leave me 5-stars on the google play store? it really helps with exposure and promotions of the app. thank youuu!
kenCode - Decentraliser @ Agorise
Matrix/Keybase/Hive/Commun/Github: @Agorise
www.PalmPay.chat

Offline Permie

  • Hero Member
  • *****
  • Posts: 606
  • BitShares is the mycelium of the financial-earth
    • View Profile
  • BitShares: krimduss
Serious congratulations for BlockPay kencode

BitShares need more business people like you
You're a pioneer

Best BitShares product. An actual economic benefit to existing fiat companies to use the bts blockchain.
 +5% +5% +5% +5% +5%
JonnyBitcoin votes for liquidity and simplicity. Make him your proxy?
BTSDEX.COM

Offline Thom

Yes, I think he is a machine :)

Well done my friend, awesome report!

Tons of updates this week!
https://github.com/kenCode-de?tab=repositories
 
BlockPay related:
 
A bug that made the app crash after selecting BTS as a Loyalty Points token has been fixed. Some unused string resources were also removed speeding the app up. A protection against a crash that seemed to be produced when no currency was being selected was put in place. And a small bug in the numerical keypad screen was fixed.
 
The hierarchy of views used to build the keypad view was using a deeply nested chain of linear layouts, which constitutes a sub-optimal design choice. Since some changes were required for this view anyways, it was decided to replace the set of nested linear layouts for a newer and more efficient component called ConstraintLayout (https://developer.android.com/reference/android/support/constraint/ConstraintLayout.html). With it is possible to design complex UI structures like the keypad view while keeping the view hierarchy relatively flat. These efficiency improvements make BlockPay run faster and more stable.
 
The QR code screen has been cleaned up and simplified.
 
The selected language was not using the required pointer in order to obtain the value from the shared resources. As a result, the app's default language was always being selected in some parts of the app, not all. This has also been fixed.
 
The Bridge has undergone some extensive upgrades too. We are hiding some tokens that were just cluttering up the settings screen. By showing less on the settings screen and automating more of the processes, like requiring the blockpay tokens for surety, it makes initial setup of the app much quicker and easier. We should have the new settings screen complete in less than 3 weeks which will really make the blockpay ambassadors and merchants happy. This will be the v1.7 release. Remember, my ultimate goal is to have a 1-step setup.
 
The numerical keypad was extended with the introduction of a "+" (plus) button, that will allow the merchant to enter a list of individual prices chained together. All the work relating to both the ConstraintLayout, some corner cases, and the introduction of the new "+" button have been finished. You will see these enhancements in the upcoming v1.5.9 release (most likely tonight or tomorrow).
 
Graphenej (https://github.com/kenCode-de/graphenej):
After some more research, it was finally possible to make the backup files generated using the graphenej library completely compatible with the web wallet and light clients. This .bin backup interoperability is now complete and will be published this week in both BlockPay v1.5.9 and the Smartcoins Wallet v1.5.14.
 
This week we also started to work on the support for direct-DEx operations. The first operation that was introduced was the limit_order_create_operation, with this commit having most of the new classes and tests. The binary serialization (required for the local tx signing procedure) is matching the serialized version of the operation produced by the cli_wallet tool, but the transaction built using this newly introduced operation is still being rejected by the network. Further tests, especially on the JSON serialization are required and should be completed this week as well.
 
C-IPFS related:
 
This week, we continued to work on tying the C-IPFS implementation to the IPFS swarm. There will probably be more commits before the end of the day, as this just about wraps it up.
 
The underlying c-libp2p was modified as follows..
 
secio protocol:
https://github.com/kenCode-de/c-libp2p/commit/6d9473069ba17a37dab71d5e33088eb62bb74f5d
https://github.com/kenCode-de/c-libp2p/commit/0e0b6b15465c224235e78f91056d5dc0accf23e3
https://github.com/kenCode-de/c-libp2p/commit/c343d2d0ad1e2d4def471064f4e7593f2f61ac88
https://github.com/kenCode-de/c-libp2p/commit/e092a0e974689fa15be17f0bc7f59c9634db1863
https://github.com/kenCode-de/c-libp2p/commit/05cc6e9bd3f025316ce4d95f080eeb21a3e57b38
https://github.com/kenCode-de/c-libp2p/commit/3d53c470a50a2a75bda41d32706b6a3bc31f7c4e
https://github.com/kenCode-de/c-libp2p/commit/a6fe0fda4765b41fb371cf48787db4038e7429bf
 
We then made the interface to streams a bit more generic:
https://github.com/kenCode-de/c-libp2p/commit/d0512d90847dbc95283e1f5f38afbda1adedccd8
https://github.com/kenCode-de/c-libp2p/commit/74d95cb696b6da141e6b751faa8abb5495d5ee45
 
c-ipfs was then modified to use the new code:
https://github.com/kenCode-de/c-ipfs/commit/cd5d347e6346e26256c1bc96b92dbb62bf741e17
https://github.com/kenCode-de/c-ipfs/commit/15a8abff9a7abd417b90a4ebda39ecfa9fac27ad
https://github.com/kenCode-de/c-ipfs/commit/43ca31385463774f2466eb55efced36a94b7d82d
 
Additional c-libp2p work finished up:
https://github.com/kenCode-de/c-libp2p/commit/0ffe73ae28202df7453be74b6502093a0c2df13b
https://github.com/kenCode-de/c-libp2p/commit/1b5b7c7cbacd354938c377788ef1e6af180b65e5
https://github.com/kenCode-de/c-libp2p/commit/018923ad0964c558a19c5d65688ab9ff503c7c55
https://github.com/kenCode-de/c-libp2p/commit/1fa0d4bd682060e5f60afbd4ff38f116d49713c7
 
Kademlia/DHT will finally be completed by tonight or tomorrow, just need to finish the callback work for returning search results.
 
Plans for the final week:
 
Lots of code cleanup now. Tidy up the comment lines, indenting and spaces, remove unused code/methods, and add efficiency wherever possible. Like I always say, every byte counts. Our v1.0.0 release will be for *nix systems and the RasPi3 first. Then the build for android the following week.
 
Android Smartcoins Wallet:
 
As you guys know, the Smartcoins Wallet is about to natively support 6 blockchains. Bitshares, Bitcoin, Dash, Litecoin, Dogecoin and Steem. In v1.7 our new streamlined Overdraft Protection feature (aka: "backup asset") will be upgraded to graphenej. In 2.0 (I'll upload a youtube vid for you guys this week I hope so that you can see the new ui/ux concepts in action) we add our c-ipfs and initial meshnet support and the rebrand of the wallet to "Carbon". Also, a big shoutout to @iHashFury for the suggestion (https://bitsharestalk.org/index.php/topic,22576.msg302196.html#msg302196)!
 
Work done this week:
  • Bitcoin support is done and tested (send/receive, balances, transactions, qr, import/backups, eReceipts, etc)
  • Change api to new server parameters
  • Testing of our altcoin fullnode servers (Dash was first, then Doge and Litecoin...)
  • Change contacts to use sqlite db
  • Changed contacts fragment, add and edit activity to work with BTC/alts
  • Changed the Send screen to enable selecting BTC/alts Contacts
  • Create base Custom Network Parameters for altcoins
Most of the upgraded UI (for multi-chain support) is ready, the thing to note is the interface is implemented with a new line for each coin right now, but this basic UI will be replaced in v2.0.0 ("Carbon"). Also the send and receive screens had to be modified to adapt to the upcoming 2.0 UI (I'll post a youtube vid so you can see our progress on it in the next week or so).
 
Work coming this next week:
  • Figure out Dash InstantSend and get it finished
  • The code we had created for the original Contacts screen needs to be cleaned up now that multi-chain support has been added
  • The network parameters in bitcoinj are used to calculate all the transactions and the addresses, which is needed to use the api, so we standardized this to use each altcoin, which in turn makes the implementations much faster
  • Upgrade our fullnode servers to support the additional coins
  • Make sure all the chains we offer native support to can also take advantage of BlockPay Loyalty Points, Overdraft Protection, eReceipts and so on
  • Testing Litecoin
  • Testing Dogecoin
  • Test and bug fix the Bridge so that users can shift between coins when desired
Stealth related:
 
We're now into week 2 of 6 for the Stealth api creation. In the UI, I have also designed a "3-way switch" that allows you to just do a Normal, Blinded, or Stealth transaction simply by flipping an animated switch. This is a compact way for users to just flip the switch and sends funds however they like. I will try to get you guys some screen shots in the next couple weeks so that you can see it in action.
 
I also am adding an option in the wallet Settings where you can choose the default setting for that switch, so that you don't always have to remember to set your transaction to Stealth, or just Blinded mode, etc. If you have ever seen that "Propose" 2-way switch when you send funds, well, just imagine that as a 3-way switch on the Send screen. Grayed out for Normal, the switch turns yellow if you flip it to Blinded, and it turns red if you flip it to Stealth mode.
 
This 3-way switch also works nicely on mobile since it is so compact, colored, etc. BlockPay merchants and users alike want an easy way to use Stealth so I went with the k.i.s.s. method on this. The further we get on the Stealth api, the more UI hooks we can make. Lots of Stealth coding to show this week:
https://github.com/kenCode-de/bitshares-core/commit/009b3e6c8e99349450349913b12a0bced6631cec
 
Besides the 3-way switch, we have also made huge progress on the database, account and contacts editor screens, and initial outlay for the automated backups feature using our c-ipfs implementation. Now that the encryption work is done, it's just down to the api and "trustless setup" algo (which we already have the plan for and will be relatively easy to implement and prove thanx to DPOS). More on that in week 6.
 
Lots of logic has been added this week too which prevents users from screwing anything up. Besides Chrome support, we are also writing the necessary code to make Stealth as portable as possible in different browsers and configurations such as Firefox and non-websql compatible browsers.
 
By the way, I don't know if you guys ever saw the original drawings that bytemaster did for Stealth when he used the "@" symbol for addresses. I use a lot of keyboard shortcuts and don't reach for my mouse much, so by having an easy way to access Stealth accounts and addresses by just typing that one character is a nice feature, so I have implemented that in the UI as well. You don't have to type it, as flipping the 3-way switch will do it for you, but I like having that option available. Not that reaching for my mouse is hard or anything..
 
Alfredo Garcia, Bitshares Core Dev update:
 
Alfredo has some monster updates done this past week. The segfault issue in the get_ticker api call has been fixed. The cause of the segfault has been found and removed but this led us to a new additional bug that was found in an api call get_trade_history used by get_ticker and get_24_volume calls.
 
Those new bugs found are being researched as we speak and we should have a solution for them as well in the coming week. In the process of a change in get_ticker and get_24_volume, calls to don't use get_trade_history or fix the get_trade_history function. So fixing this is definitely a priority too.
 
Regarding the "Socket spamming too much data." issue:
https://github.com/bitshares/bitshares-core/issues/231
 
New commits from elmato in his branch: https://github.com/elmato/bitshares-2/tree/no-spam-sub-function
 
We tested and setup a node for sigve to make the final tests before the merge. Everything is working great now so as long as our final tests work as expected, we will finally commit this one (hopefully by monday)
 
Regarding "Can operation_results please show the operation id(s) of all ops in the tx?" issue:
https://github.com/bitshares/bitshares-core/issues/243
This one is now in progress.
 
Regarding "https://github.com/bitshares/bitshares-core/issues/159" issue:
https://github.com/bitshares/bitshares-core/issues/159
This one is done as well and I will close it in the next 24 hours.
 
Here is a list of some of the other bitshares-core issues that Alfredo is tackling right now:
https://github.com/bitshares/bitshares-core/issues?q=is%3Aissue+is%3Aopen+sort%3Acreated-asc
 
As for new features, I would like Alfredo to also work on Dividends, Black Swan prevention and recovery, advanced Trading functions to DEx (Margin Trading, Stop Loss, Trailing Stop etc.), selling/dumping a UIA that you no longer want, Worker proposal upgrade (as per Data and Jonny's ideas), Recurring and Scheduled Payments feature, make it so that FBA's don't always need a hardfork, and a lot more. If you have ideas for new features, please contact chris4210 since he maintains the Bitshares wishlist.
 
Over the weekend I will also publish more app updates to google play for both BlockPay and the Smartcoins Wallet so stay tuned if you want to see all the new stuff we've been working on. As usual, I will post the download links here for you guys too.
Injustice anywhere is a threat to justice everywhere - MLK |  Verbaltech2 Witness Reports: https://bitsharestalk.org/index.php/topic,23902.0.html


Offline kenCode

  • Hero Member
  • *****
  • Posts: 2283
    • View Profile
    • Agorise
Tons of updates this week!
https://github.com/kenCode-de?tab=repositories
 
BlockPay related:
 
A bug that made the app crash after selecting BTS as a Loyalty Points token has been fixed. Some unused string resources were also removed speeding the app up. A protection against a crash that seemed to be produced when no currency was being selected was put in place. And a small bug in the numerical keypad screen was fixed.
 
The hierarchy of views used to build the keypad view was using a deeply nested chain of linear layouts, which constitutes a sub-optimal design choice. Since some changes were required for this view anyways, it was decided to replace the set of nested linear layouts for a newer and more efficient component called ConstraintLayout (https://developer.android.com/reference/android/support/constraint/ConstraintLayout.html). With it is possible to design complex UI structures like the keypad view while keeping the view hierarchy relatively flat. These efficiency improvements make BlockPay run faster and more stable.
 
The QR code screen has been cleaned up and simplified.
 
The selected language was not using the required pointer in order to obtain the value from the shared resources. As a result, the app's default language was always being selected in some parts of the app, not all. This has also been fixed.
 
The Bridge has undergone some extensive upgrades too. We are hiding some tokens that were just cluttering up the settings screen. By showing less on the settings screen and automating more of the processes, like requiring the blockpay tokens for surety, it makes initial setup of the app much quicker and easier. We should have the new settings screen complete in less than 3 weeks which will really make the blockpay ambassadors and merchants happy. This will be the v1.7 release. Remember, my ultimate goal is to have a 1-step setup.
 
The numerical keypad was extended with the introduction of a "+" (plus) button, that will allow the merchant to enter a list of individual prices chained together. All the work relating to both the ConstraintLayout, some corner cases, and the introduction of the new "+" button have been finished. You will see these enhancements in the upcoming v1.5.9 release (most likely tonight or tomorrow).
 
Graphenej (https://github.com/kenCode-de/graphenej):
After some more research, it was finally possible to make the backup files generated using the graphenej library completely compatible with the web wallet and light clients. This .bin backup interoperability is now complete and will be published this week in both BlockPay v1.5.9 and the Smartcoins Wallet v1.5.14.
 
This week we also started to work on the support for direct-DEx operations. The first operation that was introduced was the limit_order_create_operation, with this commit having most of the new classes and tests. The binary serialization (required for the local tx signing procedure) is matching the serialized version of the operation produced by the cli_wallet tool, but the transaction built using this newly introduced operation is still being rejected by the network. Further tests, especially on the JSON serialization are required and should be completed this week as well.
 
C-IPFS related:
 
This week, we continued to work on tying the C-IPFS implementation to the IPFS swarm. There will probably be more commits before the end of the day, as this just about wraps it up.
 
The underlying c-libp2p was modified as follows..
 
secio protocol:
https://github.com/kenCode-de/c-libp2p/commit/6d9473069ba17a37dab71d5e33088eb62bb74f5d
https://github.com/kenCode-de/c-libp2p/commit/0e0b6b15465c224235e78f91056d5dc0accf23e3
https://github.com/kenCode-de/c-libp2p/commit/c343d2d0ad1e2d4def471064f4e7593f2f61ac88
https://github.com/kenCode-de/c-libp2p/commit/e092a0e974689fa15be17f0bc7f59c9634db1863
https://github.com/kenCode-de/c-libp2p/commit/05cc6e9bd3f025316ce4d95f080eeb21a3e57b38
https://github.com/kenCode-de/c-libp2p/commit/3d53c470a50a2a75bda41d32706b6a3bc31f7c4e
https://github.com/kenCode-de/c-libp2p/commit/a6fe0fda4765b41fb371cf48787db4038e7429bf
 
We then made the interface to streams a bit more generic:
https://github.com/kenCode-de/c-libp2p/commit/d0512d90847dbc95283e1f5f38afbda1adedccd8
https://github.com/kenCode-de/c-libp2p/commit/74d95cb696b6da141e6b751faa8abb5495d5ee45
 
c-ipfs was then modified to use the new code:
https://github.com/kenCode-de/c-ipfs/commit/cd5d347e6346e26256c1bc96b92dbb62bf741e17
https://github.com/kenCode-de/c-ipfs/commit/15a8abff9a7abd417b90a4ebda39ecfa9fac27ad
https://github.com/kenCode-de/c-ipfs/commit/43ca31385463774f2466eb55efced36a94b7d82d
 
Additional c-libp2p work finished up:
https://github.com/kenCode-de/c-libp2p/commit/0ffe73ae28202df7453be74b6502093a0c2df13b
https://github.com/kenCode-de/c-libp2p/commit/1b5b7c7cbacd354938c377788ef1e6af180b65e5
https://github.com/kenCode-de/c-libp2p/commit/018923ad0964c558a19c5d65688ab9ff503c7c55
https://github.com/kenCode-de/c-libp2p/commit/1fa0d4bd682060e5f60afbd4ff38f116d49713c7
 
Kademlia/DHT will finally be completed by tonight or tomorrow, just need to finish the callback work for returning search results.
 
Plans for the final week:
 
Lots of code cleanup now. Tidy up the comment lines, indenting and spaces, remove unused code/methods, and add efficiency wherever possible. Like I always say, every byte counts. Our v1.0.0 release will be for *nix systems and the RasPi3 first. Then the build for android the following week.
 
Android Smartcoins Wallet:
 
As you guys know, the Smartcoins Wallet is about to natively support 6 blockchains. Bitshares, Bitcoin, Dash, Litecoin, Dogecoin and Steem. In v1.7 our new streamlined Overdraft Protection feature (aka: "backup asset") will be upgraded to graphenej. In 2.0 (I'll upload a youtube vid for you guys this week I hope so that you can see the new ui/ux concepts in action) we add our c-ipfs and initial meshnet support and the rebrand of the wallet to "Carbon". Also, a big shoutout to @iHashFury for the suggestion (https://bitsharestalk.org/index.php/topic,22576.msg302196.html#msg302196)!
 
Work done this week:
  • Bitcoin support is done and tested (send/receive, balances, transactions, qr, import/backups, eReceipts, etc)
  • Change api to new server parameters
  • Testing of our altcoin fullnode servers (Dash was first, then Doge and Litecoin...)
  • Change contacts to use sqlite db
  • Changed contacts fragment, add and edit activity to work with BTC/alts
  • Changed the Send screen to enable selecting BTC/alts Contacts
  • Create base Custom Network Parameters for altcoins
Most of the upgraded UI (for multi-chain support) is ready, the thing to note is the interface is implemented with a new line for each coin right now, but this basic UI will be replaced in v2.0.0 ("Carbon"). Also the send and receive screens had to be modified to adapt to the upcoming 2.0 UI (I'll post a youtube vid so you can see our progress on it in the next week or so).
 
Work coming this next week:
  • Figure out Dash InstantSend and get it finished
  • The code we had created for the original Contacts screen needs to be cleaned up now that multi-chain support has been added
  • The network parameters in bitcoinj are used to calculate all the transactions and the addresses, which is needed to use the api, so we standardized this to use each altcoin, which in turn makes the implementations much faster
  • Upgrade our fullnode servers to support the additional coins
  • Make sure all the chains we offer native support to can also take advantage of BlockPay Loyalty Points, Overdraft Protection, eReceipts and so on
  • Testing Litecoin
  • Testing Dogecoin
  • Test and bug fix the Bridge so that users can shift between coins when desired
Stealth related:
 
We're now into week 2 of 6 for the Stealth api creation. In the UI, I have also designed a "3-way switch" that allows you to just do a Normal, Blinded, or Stealth transaction simply by flipping an animated switch. This is a compact way for users to just flip the switch and sends funds however they like. I will try to get you guys some screen shots in the next couple weeks so that you can see it in action.
 
I also am adding an option in the wallet Settings where you can choose the default setting for that switch, so that you don't always have to remember to set your transaction to Stealth, or just Blinded mode, etc. If you have ever seen that "Propose" 2-way switch when you send funds, well, just imagine that as a 3-way switch on the Send screen. Grayed out for Normal, the switch turns yellow if you flip it to Blinded, and it turns red if you flip it to Stealth mode.
 
This 3-way switch also works nicely on mobile since it is so compact, colored, etc. BlockPay merchants and users alike want an easy way to use Stealth so I went with the k.i.s.s. method on this. The further we get on the Stealth api, the more UI hooks we can make. Lots of Stealth coding to show this week:
https://github.com/kenCode-de/bitshares-core/commit/009b3e6c8e99349450349913b12a0bced6631cec
 
Besides the 3-way switch, we have also made huge progress on the database, account and contacts editor screens, and initial outlay for the automated backups feature using our c-ipfs implementation. Now that the encryption work is done, it's just down to the api and "trustless setup" algo (which we already have the plan for and will be relatively easy to implement and prove thanx to DPOS). More on that in week 6.
 
Lots of logic has been added this week too which prevents users from screwing anything up. Besides Chrome support, we are also writing the necessary code to make Stealth as portable as possible in different browsers and configurations such as Firefox and non-websql compatible browsers.
 
By the way, I don't know if you guys ever saw the original drawings that bytemaster did for Stealth when he used the "@" symbol for addresses. I use a lot of keyboard shortcuts and don't reach for my mouse much, so by having an easy way to access Stealth accounts and addresses by just typing that one character is a nice feature, so I have implemented that in the UI as well. You don't have to type it, as flipping the 3-way switch will do it for you, but I like having that option available. Not that reaching for my mouse is hard or anything..
 
Alfredo Garcia, Bitshares Core Dev update:
 
Alfredo has some monster updates done this past week. The segfault issue in the get_ticker api call has been fixed. The cause of the segfault has been found and removed but this led us to a new additional bug that was found in an api call get_trade_history used by get_ticker and get_24_volume calls.
 
Those new bugs found are being researched as we speak and we should have a solution for them as well in the coming week. In the process of a change in get_ticker and get_24_volume, calls to don't use get_trade_history or fix the get_trade_history function. So fixing this is definitely a priority too.
 
Regarding the "Socket spamming too much data." issue:
https://github.com/bitshares/bitshares-core/issues/231
 
New commits from elmato in his branch: https://github.com/elmato/bitshares-2/tree/no-spam-sub-function
 
We tested and setup a node for sigve to make the final tests before the merge. Everything is working great now so as long as our final tests work as expected, we will finally commit this one (hopefully by monday)
 
Regarding "Can operation_results please show the operation id(s) of all ops in the tx?" issue:
https://github.com/bitshares/bitshares-core/issues/243
This one is now in progress.
 
Regarding "https://github.com/bitshares/bitshares-core/issues/159" issue:
https://github.com/bitshares/bitshares-core/issues/159
This one is done as well and I will close it in the next 24 hours.
 
Here is a list of some of the other bitshares-core issues that Alfredo is tackling right now:
https://github.com/bitshares/bitshares-core/issues?q=is%3Aissue+is%3Aopen+sort%3Acreated-asc
 
As for new features, I would like Alfredo to also work on Dividends, Black Swan prevention and recovery, advanced Trading functions to DEx (Margin Trading, Stop Loss, Trailing Stop etc.), selling/dumping a UIA that you no longer want, Worker proposal upgrade (as per Data and Jonny's ideas), Recurring and Scheduled Payments feature, make it so that FBA's don't always need a hardfork, and a lot more. If you have ideas for new features, please contact chris4210 since he maintains the Bitshares wishlist.
 
Over the weekend I will also publish more app updates to google play for both BlockPay and the Smartcoins Wallet so stay tuned if you want to see all the new stuff we've been working on. As usual, I will post the download links here for you guys too.
kenCode - Decentraliser @ Agorise
Matrix/Keybase/Hive/Commun/Github: @Agorise
www.PalmPay.chat

Offline CLains

  • Hero Member
  • *****
  • Posts: 2606
    • View Profile
  • BitShares: clains
If we keep moving at this pace, I hope to have the first Stealth testnet online for public testing in less than 6 weeks. This will include the new core, the api with functional UI, and conversion of most of the Rust code for our "trustless setup" algo.
 
I know 6 weeks sounds like an eternity, but I want this to be done right. The UI/UX has to be perfect too, or else we will never get any mass adoption. First impressions are everything.

Awesome update kenCode. Especially looking forward to this :D

Offline ebit

  • Committee member
  • Hero Member
  • *
  • Posts: 1854
    • View Profile
  • BitShares: ebit
telegram:ebit521
https://weibo.com/ebiter