[ANN - Pre-ICO] BlockPay - Zero Cost, digital currency Point-Of-Sale systems

[Chris4210x]

The only Person Who Seems to be "super excited" About this Projekt is you chris.... 

Each project needs a crazy visionary leader right

Did you know that we are actually transforming BlockPay with C-IPFS and are now able to install the BlockPay payment function on every hardware device on  the planet?! We could preinstall BlockPay in TV´s, printer, e-plugs, smart locks... micro transaction and multi chain point of sale systems are now coming to IOT thanks to BlockPay... Mindblown

[DaddyH]

The only Person Who Seems to be "super excited" About this Projekt is you chris.... 

Each project needs a crazy visionary leader right

Did you know that we are actually transforming BlockPay with C-IPFS and are now able to install the BlockPay payment function on every hardware device on  the planet?! We could preinstall BlockPay in TV´s, printer, e-plugs, smart locks... micro transaction and multi chain point of sale systems are now coming to IOT thanks to BlockPay... Mindblown

When you put it like that, it is rather impressive.
Listing on a major exchange might help the price along though

[animalroam]

I understand that it's more important to develop than to get on an exchange, but having the price tank so much is also bad for the shares.

how so?

It may be a morale obstruction to the Blockpay team and to its investors, who may in turn not support the project as much due to its low value.

[Deanero]

I understand that it's more important to develop than to get on an exchange, but having the price tank so much is also bad for the shares.

how so?

It may be a morale obstruction to the Blockpay team and to its investors, who may in turn not support the project as much due to its low value.

I am invested in Blockpay as I believe in the vision and the fact that's it's a working product.

However, being only on open ledger seems counter productive. Blockpay should at least be listed on Bittrex also.

It's a great project and deserves more recognition, and in my opinion is severely undervalued, but with such low volume and a low level of traders trading on openledger, the price is going to continue to be in a slump.

Please add to Bittrex, the project is ready to be on a higher volume exchange.

Is there any particular reason why you have not added BlockPay to another exchange yet?

[Deanero]

This has got to be the most inactive thread for a project on bitcointalk.

Unless there's another thread I'm missing?

[DaddyH]

This has got to be the most inactive thread for a project on bitcointalk.

Unless there's another thread I'm missing?

after the initial buzz, things seems to have gone very quiet. I dont doubt there's some good work going on in the background. But a Community Support person should be keeping this thread alive.

[Chris4210x]

I understand that it's more important to develop than to get on an exchange, but having the price tank so much is also bad for the shares.

how so?

It may be a morale obstruction to the Blockpay team and to its investors, who may in turn not support the project as much due to its low value.

I am invested in Blockpay as I believe in the vision and the fact that's it's a working product.

However, being only on open ledger seems counter productive. Blockpay should at least be listed on Bittrex also.

It's a great project and deserves more recognition, and in my opinion is severely undervalued, but with such low volume and a low level of traders trading on openledger, the price is going to continue to be in a slump.

Please add to Bittrex, the project is ready to be on a higher volume exchange.

Is there any particular reason why you have not added BlockPay to another exchange yet?

Hi Deanero,

I am already talking with HitBTC and Bittrex about adding BlockPay tokens to their exchanges. I am hope we can launch soon with them too. Meanwhile I am looking forward to the new OpenLeder trading interface that should be released on November 15th. I expect it to be way cleaner and to make trading super easy. I heard that they will even have two different themes, one for beginners and one for expert traders. So that everybody can buy and sell on the exchange with a few clips. Also deposit and withdraw will be redesigned and easier.

We will keep you up to date with the BlockPay trading exchanges.

This has got to be the most inactive thread for a project on bitcointalk.

Unless there's another thread I'm missing?

No, we just have one thread with regular updates right now and that is this one. I keep you posted about the latest developments Another good source for updates is our twitter account @blockpay_ch or on our youtube channel with our VBlog.


cheers Chris

[favdesu]

This has got to be the most inactive thread for a project on bitcointalk.

Unless there's another thread I'm missing?

after the initial buzz, things seems to have gone very quiet. I dont doubt there's some good work going on in the background. But a Community Support person should be keeping this thread alive.

give them a break. let them work, it's much better than keeping a bitcointalk thread alive...

[DaddyH]

This has got to be the most inactive thread for a project on bitcointalk.

Unless there's another thread I'm missing?

after the initial buzz, things seems to have gone very quiet. I dont doubt there's some good work going on in the background. But a Community Support person should be keeping this thread alive.

give them a break. let them work, it's much better than keeping a bitcointalk thread alive...

What?

[Chris4210x]

Hi guys, I want to give you a short update about BlockPay and what we have been working on the last few days.

We had to fire our old marketing partners because they did not perform the way we wanted. We now added 2 more people to the core team who will be in charge of all social media channels and keep reporting about our journey. One of the first articles is out already, check out https://steemit.com/blockpay/@bitshares-munich/the-faces-behind-blockpay-christoph-and-rodrigo .

For direct updates please also follow us on Twitter https://twitter.com/BlockPay_ch and on Facebook https://facebook.com/blockpayde and on Steemit https://steemit.com/@bitshares-munich

Latest Development
Let us take a look at the current software development. We are making great process in the IPFS in C development and further decentralizing the BlockPay core and building up the BlockPay engine. This new DAP structure allows us to install BlockPay on any kind of hardware! Not only on Android and iOS but also on a raspberry pi´s and other mainframes. Imagine you could pay with your Bitcoin at vending machines, petrol stations, power sockets, doors, etc.
We are already talking with industry partners for upcoming integration.

On the other side, we are working on a redesign of the current UI/UX to increase merchant adoption. The onboarding process gets redesigned as well as the settings cleaned out. I will soon share some first design mockups to the community.

Meanwhile, we are ramping up development work with stealth transaction on the Bitshares blockchain. We are now able to hide (sender,receiver,amount,memo field, meta data) from blockchain explorers. Only a timestamp will be left. Stealth is a highly requested feature for all merchants who want to move corporate funds on a blockchain. With this feature, we actually build a hybrid between a public and a private blockchain and give the whole industry a new option to store and move funds on a blockchain. Together with a scalable blockchain, stealth transactions gonna be faster, more secure, more private and easier to use than ZCash or Monero. More exciting news about our development here in the following weeks.

cheers chris4210

[rawnetics]

Hi guys, I want to give you a short update about BlockPay and what we have been working on the last few days.

We had to fire our old marketing partners because they did not perform the way we wanted. We now added 2 more people to the core team who will be in charge of all social media channels and keep reporting about our journey. One of the first articles is out already, check out https://steemit.com/blockpay/@bitshares-munich/the-faces-behind-blockpay-christoph-and-rodrigo .

For direct updates please also follow us on Twitter https://twitter.com/BlockPay_ch and on Facebook https://facebook.com/blockpayde and on Steemit https://steemit.com/@bitshares-munich

Latest Development
Let us take a look at the current software development. We are making great process in the IPFS in C development and further decentralizing the BlockPay core and building up the BlockPay engine. This new DAP structure allows us to install BlockPay on any kind of hardware! Not only on Android and iOS but also on a raspberry pi´s and other mainframes. Imagine you could pay with your Bitcoin at vending machines, petrol stations, power sockets, doors, etc.
We are already talking with industry partners for upcoming integration.

On the other side, we are working on a redesign of the current UI/UX to increase merchant adoption. The onboarding process gets redesigned as well as the settings cleaned out. I will soon share some first design mockups to the community.

Meanwhile, we are ramping up development work with stealth transaction on the Bitshares blockchain. We are now able to hide (sender,receiver,amount,memo field, meta data) from blockchain explorers. Only a timestamp will be left. Stealth is a highly requested feature for all merchants who want to move corporate funds on a blockchain. With this feature, we actually build a hybrid between a public and a private blockchain and give the whole industry a new option to store and move funds on a blockchain. Together with a scalable blockchain, stealth transactions gonna be faster, more secure, more private and easier to use than ZCash or Monero. More exciting news about our development here in the following weeks.

cheers chris4210

Fantastic news! Looking forward to the coming weeks, thanks for the update!

[animalroam]

I'm glad development is still pretty active. Please continue to give us weekly/bi-weekly updates in order to keep the community engaged.

[kellendil]

Nice updates and weekly updates would be very good.

[clickerz]

The only Person Who Seems to be "super excited" About this Projekt is you chris.... 

Each project needs a crazy visionary leader right

Did you know that we are actually transforming BlockPay with C-IPFS and are now able to install the BlockPay payment function on every hardware device on  the planet?! We could preinstall BlockPay in TV´s, printer, e-plugs, smart locks... micro transaction and multi chain point of sale systems are now coming to IOT thanks to BlockPay... Mindblown

This is a good projrct if fully implemented. I am also familiar with Point of Sail, and if this project materialzed this is a good innovation. I am hoping a zero confirmations, real time updating of wallets LOL

[DaddyH]

It's all gone quiet.
What's happening? Are the devs on Slack?

[Chris4210x]

It's all gone quiet.
What's happening? Are the devs on Slack?

We have daily updates on our Social Media channels. Please check

www.Facebook.com/blockpayde/
www.twitter.com/blockpay_ch
www.steemit.com/created/BlockPay
https://www.youtube.com/channel/UCJl3M4kuMaihU-yUQvnexkg

We also have a weekly dev update every Friday. Here is the latest update:

https://bitsharestalk.org/index.php/topic,22576.120.html

TONS of work done this week:
https://github.com/kenCode-de?tab=repositories
 
C-IPFS and BlockPay related:
 
Work continued on the development of c-ipfs, in the area of data storage. Blocks are now written to both the lightningdb database, and the /blocks directory. We also wrote tests to cover more code, and adjusted existing code to clean up memory leaks. Valgrind now runs fairly clean over our tests of c-ipfs.
 
The difference between what is stored in the /blocks directory and what is stored in the database is not totally clear yet, but this week will hopefully uncover the rest of it. While successfully writing to block storage is a big accomplishment, block retrieval isn't finished yet. This task is minor in complexity though. Also, block storage must now be leveraged to take on the MerkleDAG and the unixfs code that runs on top of it. This will allow for files to be placed in namespaces (aka: directories), be broken into pieces, and read/found by local and remote BlockPay or mobile wallet clients.
 
More c-ipfs and c-ipns (was running very slow) commits:
https://github.com/kenCode-de/c-ipfs/commit/8da6e2df690d698067b2cb5615cce12f00a1f3bd
https://github.com/kenCode-de/c-ipfs/commit/0f5964ad3cb6fca94651001b43e76ae0ef3032ec
https://github.com/kenCode-de/c-ipfs/commit/ac4cc8feaaef747295b8705fa7f1b6d43d72f4dd
https://github.com/kenCode-de/c-ipfs/commit/a21330af436c0b9c6e8628f6f15acf1f0e2d37c0
https://github.com/kenCode-de/c-ipfs/commit/47e035e29f8d4870b6a9def0cb1a397cb91ac5bf
https://github.com/kenCode-de/c-ipfs/commit/d761e6062b7e92b69b604d96e42b80d58f7ebad9
https://github.com/kenCode-de/c-ipfs/commit/cba5839f5623af89bd969a959de1a7b0012bf908
https://github.com/kenCode-de/c-ipfs/commit/75f86b4107f87489efcd7b4ebea230cb8e24dd71
https://github.com/kenCode-de/c-ipfs/commit/8f686f6115c613614382e4599d73aa5e8d118bd6
https://github.com/kenCode-de/c-ipfs/commit/e89b5515c24ed32334f7bff04224b79b19257e7e
https://github.com/kenCode-de/c-ipfs/commit/a4b6a14ea524689556e9f9cf927a3519c64c0e24
https://github.com/kenCode-de/c-ipfs/commit/9ba3112b9705d48b7a333f43a4d11a45c5ad5d8f
https://github.com/kenCode-de/c-ipfs/commit/33afac194a0d6e6f153d3408ebacb3a2565ba030
https://github.com/kenCode-de/c-ipfs/commit/316c880bd1354a4649302c4429559c9f681de69e
 
We've been redesigning go-ipld-node + go-ipfs/merkledag/node + go-ipld, etc. to actually work together in C as they can't be preserved in go's form, the languages differ too much. Creating merkledag nodes, which can either be links to other nodes or data nodes, these will process data stored in files in the future (with merkledag done) assure validity of data, etc.
 
Android Smartcoins Wallet and security audits:
 
This week we streamlined a bunch of code and moved more of it to the client side so that now hardly any trips to the server need to be made. By letting the client do more of the work, it has sped the app up a bit and greatly reduced bandwidth utilization. BIP39 support has been added too (real words, instead of brainkey "weird" words). During the security audit, we have also made some other improvements this week:
Improved Websocket communication
Create Account Activity
Debugging Python server-side components
Encrypt/Decrypt AES
Compress/Decompress LZMA library
Export / Import Bin File Library, compatible with old bin files now
Export bin file Activity
Import bin file Activity (in progress)
A bug with the transfer transaction was fixed. The problem happened randomly and because of that was not caught initially. The reason has to do with the strictness of the graphene network on its approval of signatures. Sadly the bitcoinj doesn't provide support for non-deterministic signature generation, so we had to be creative when coming up with a solution. A valid compromise was deemed to slightly change the expiration time of the transaction in order to generate a valid signature. It is important to note however that this has no visible impact whatsoever for the user and the transaction gets processed super fast as always.
 
Improvements were made to the QR-code generation mechanism. The reliance on a server for the QR generation, encoding and compression of the eReceipt data has been dropped. This has had a dramatic improvement in the speed of the generation of a QR-code. And of course to be able to generate the QR-code while off-line is also a major advantage in speed and bandwidth utilization. The corresponding change in the procedure of decompression and decoding the data when reading a QR-code with the camera also had to be adjusted, since a server was being used there too.
 
graphenej in progress, BIP39 support added and now being tested.
 
Stealth related:
 
Libsnark is now fully integrated, replaced libsodium crypto primitives, finished notes encryption/decryption and fully tested. UI now being worked on, will upload more screenshots soon.

BlockPay and our other products are growing rapidly and we make amazing progress with IPFS in C! Due to security reasons are our main developers in no chat channels. We only work with the best and we don´t want to distract them from their work.

Cheers Chris

[DaddyH]

It's all gone quiet.
What's happening? Are the devs on Slack?

We have daily updates on our Social Media channels. Please check

www.Facebook.com/blockpayde/
www.twitter.com/blockpay_ch
www.steemit.com/created/BlockPay
https://www.youtube.com/channel/UCJl3M4kuMaihU-yUQvnexkg

We also have a weekly dev update every Friday. Here is the latest update:

https://bitsharestalk.org/index.php/topic,22576.120.html

TONS of work done this week:
https://github.com/kenCode-de?tab=repositories
 
C-IPFS and BlockPay related:
 
Work continued on the development of c-ipfs, in the area of data storage. Blocks are now written to both the lightningdb database, and the /blocks directory. We also wrote tests to cover more code, and adjusted existing code to clean up memory leaks. Valgrind now runs fairly clean over our tests of c-ipfs.
 
The difference between what is stored in the /blocks directory and what is stored in the database is not totally clear yet, but this week will hopefully uncover the rest of it. While successfully writing to block storage is a big accomplishment, block retrieval isn't finished yet. This task is minor in complexity though. Also, block storage must now be leveraged to take on the MerkleDAG and the unixfs code that runs on top of it. This will allow for files to be placed in namespaces (aka: directories), be broken into pieces, and read/found by local and remote BlockPay or mobile wallet clients.
 
More c-ipfs and c-ipns (was running very slow) commits:
https://github.com/kenCode-de/c-ipfs/commit/8da6e2df690d698067b2cb5615cce12f00a1f3bd
https://github.com/kenCode-de/c-ipfs/commit/0f5964ad3cb6fca94651001b43e76ae0ef3032ec
https://github.com/kenCode-de/c-ipfs/commit/ac4cc8feaaef747295b8705fa7f1b6d43d72f4dd
https://github.com/kenCode-de/c-ipfs/commit/a21330af436c0b9c6e8628f6f15acf1f0e2d37c0
https://github.com/kenCode-de/c-ipfs/commit/47e035e29f8d4870b6a9def0cb1a397cb91ac5bf
https://github.com/kenCode-de/c-ipfs/commit/d761e6062b7e92b69b604d96e42b80d58f7ebad9
https://github.com/kenCode-de/c-ipfs/commit/cba5839f5623af89bd969a959de1a7b0012bf908
https://github.com/kenCode-de/c-ipfs/commit/75f86b4107f87489efcd7b4ebea230cb8e24dd71
https://github.com/kenCode-de/c-ipfs/commit/8f686f6115c613614382e4599d73aa5e8d118bd6
https://github.com/kenCode-de/c-ipfs/commit/e89b5515c24ed32334f7bff04224b79b19257e7e
https://github.com/kenCode-de/c-ipfs/commit/a4b6a14ea524689556e9f9cf927a3519c64c0e24
https://github.com/kenCode-de/c-ipfs/commit/9ba3112b9705d48b7a333f43a4d11a45c5ad5d8f
https://github.com/kenCode-de/c-ipfs/commit/33afac194a0d6e6f153d3408ebacb3a2565ba030
https://github.com/kenCode-de/c-ipfs/commit/316c880bd1354a4649302c4429559c9f681de69e
 
We've been redesigning go-ipld-node + go-ipfs/merkledag/node + go-ipld, etc. to actually work together in C as they can't be preserved in go's form, the languages differ too much. Creating merkledag nodes, which can either be links to other nodes or data nodes, these will process data stored in files in the future (with merkledag done) assure validity of data, etc.
 
Android Smartcoins Wallet and security audits:
 
This week we streamlined a bunch of code and moved more of it to the client side so that now hardly any trips to the server need to be made. By letting the client do more of the work, it has sped the app up a bit and greatly reduced bandwidth utilization. BIP39 support has been added too (real words, instead of brainkey "weird" words). During the security audit, we have also made some other improvements this week:
Improved Websocket communication
Create Account Activity
Debugging Python server-side components
Encrypt/Decrypt AES
Compress/Decompress LZMA library
Export / Import Bin File Library, compatible with old bin files now
Export bin file Activity
Import bin file Activity (in progress)
A bug with the transfer transaction was fixed. The problem happened randomly and because of that was not caught initially. The reason has to do with the strictness of the graphene network on its approval of signatures. Sadly the bitcoinj doesn't provide support for non-deterministic signature generation, so we had to be creative when coming up with a solution. A valid compromise was deemed to slightly change the expiration time of the transaction in order to generate a valid signature. It is important to note however that this has no visible impact whatsoever for the user and the transaction gets processed super fast as always.
 
Improvements were made to the QR-code generation mechanism. The reliance on a server for the QR generation, encoding and compression of the eReceipt data has been dropped. This has had a dramatic improvement in the speed of the generation of a QR-code. And of course to be able to generate the QR-code while off-line is also a major advantage in speed and bandwidth utilization. The corresponding change in the procedure of decompression and decoding the data when reading a QR-code with the camera also had to be adjusted, since a server was being used there too.
 
graphenej in progress, BIP39 support added and now being tested.
 
Stealth related:
 
Libsnark is now fully integrated, replaced libsodium crypto primitives, finished notes encryption/decryption and fully tested. UI now being worked on, will upload more screenshots soon.

BlockPay and our other products are growing rapidly and we make amazing progress with IPFS in C! Due to security reasons are our main developers in no chat channels. We only work with the best and we don´t want to distract them from their work.

Cheers Chris

Thanks for the update. Do you have someone to keep this thread up-to-date also? I can see you have other platforms covered, however Bitcontalk (IMO) is still a good outlet for project news and developments.

[Chris4210x]

Sure, We will ramp up the news updates here too. I am looking for the best way to keep you all up to date. Our Social Media channels are full

[Chris4210x]

Weekly Development update from us

C-IPFS and BlockPay related:
 
C-IPFS merkledag and data storage is under heavy development. Working with the "protobuf" protocol from google (data stream called Marshal and Unmarshal) was a requirement for storage (and probably networking in the near future), and we completed a very basic implementation of this late last night. We also added roll your own encode/decode, with helpers to make it easier. More features will need to be added as the use cases evolve, but this will be enough for now, for our needs.
 
Storage is a bear. At times it feels as if we're walking in mud. But then things start coming together on it. We're trying to be careful to not waste time on things we won’t be using.
 
Nodes with links will be finished up this coming week. Once nodes are a bit more finalized, namespaces (aka: directories) will need to be handled. These are not easy tasks, and are time-consuming. This coming week more of the storage "todos" are completed and we can move forward with the new BlockPay Core integrations.
 
More c-ipfs and c-ipns(lots of speed improvements thanx to the protobuf work) commits:
https://github.com/kenCode-de/c-ipfs/commit/496ae3ec6c13d1aaab1a630d8e7e8c425175d907
https://github.com/kenCode-de/c-ipfs/commit/f8723eb8c741a02dab3e7cc2096e989c27cb3425
https://github.com/kenCode-de/c-ipfs/commit/84f24797f4485b7b3eff14a99501a50a40f1fe9b
https://github.com/kenCode-de/c-ipfs/commit/7a3d0c5e0bf241d6126a125fc19fa8b3460b9af5
https://github.com/kenCode-de/c-ipfs/commit/73a76907258b1842dc77428f8cf756b3f7037b0a
https://github.com/kenCode-de/c-ipfs/commit/786bd5d80b729f33f0a97f331e0cdecfc8a87b49
 
C-IPFS to CJDNS protocol will be finished this week for our meshnet support. Everything becomes a node. Will reveal more on this later. The cryptography and IPv6 stuff should be done by tuesday. Tamper-resistance is built-in to C-IPFS, so this turned out to be the perfect marriage. If someone tries to hurt or stop BlockPay via http, ssl, dns, ddos or even killing the ISP itself, BlockPay now has its Plan B ready to go. (yeah, I have a lot of tinfoil)
 
Sealed up memory leaks and finished dnslink. Tons of additional work being performed/finished up this week on c-ipld (linked data), c-ipns, namesys, path and the command line interpreter.
 
We are also speeding up the Bridge (for shifting bitcoins/altcoins into Smartcoins, account creation etc) and I hired a UX girl to give the look a bit of a facelift in the next major version release, and make my dream of a 1-step setup a reality.
 
Android Smartcoins Wallet and security audits:
 
Added support for the 'account_update_operation' into our graphenej library being developed to enclose all graphene-related functionalities that might be re-used in other android (or java powered) projects. With this operation, it will now be possible to change permissions of any given account. The most relevant classes here are the AccountUpdateOperation, Authority and AccountOptions. I will post our graphenej open source on my github page once it's ready. This weekend I am doing a lot of beta testing first.
 
With this in place in the library it is now possible (and has been fully tested) to swap all keys for the owner, active and memo fields. It should also be possible (however this still has to be tested) to add an account as the authority for another account. For now only key authentication has been fully tested.
 
The immediate use for this newly supported feature is the swap of old keys for fresh new ones. And it will also be possible to give the user the possibility to change the controlling keys any time he/she desires.
 
More features updated:

• Import new .bin (since we are adding support for 6 additional blockchains)
• Export/Import compatibility with old .bin files
• Encode/Decode Memo Operations (this was a living hell)
• Beta testing debug apk's before we relaunch on google play
• Testing new form of websocket for multiple accounts
• The new client-side version-10 QR codes are working perfectly
• BIP39 is now fully supported and will work with the additional 6 chains
• Support added for importing/exporting to/from web wallets and light clients

Hopefully publishing the Smartcoins Wallet to google play tonight or monday.
 
Stealth related:
 
Finished up Stealth memo encryption/decryption, running final tests this week. UI now being worked on, will upload more screenshots soon.

And our latest videos

https://youtu.be/kkg96zpiUf0
https://www.facebook.com/blockpayde/videos/1518653258163909/

Our latest articles:

https://steemit.com/news/@bitshares-munich/how-blockpay-is-transforming-ipfs
https://steemit.com/news/@bitshares-munich/why-must-businesses-choose-to-accept-digital-currencies-now-rather-than-wait-for-mass-customer-adoption-of-digital-currencies


See you around!

Cheers Chris4210

[kellendil]

İ hope for a successful launch on bittrex and polo. Blockpay is a great project from Germany.