Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - blockchainprojectsbv

Pages: [1]
1
Stakeholder Proposals / [Draft][Worker Proposal] Global Marketing Board
« on: September 06, 2019, 02:13:12 pm »
Dear BitShares Community,

we have a new proposal that we would like to show the community and ask for feedback.


At this point, everything is open and we are happy for any and all constructive feedback.

Please note that some parts in the Chinese translation are still in English, once we have that corrected we will publish it also in the Chinese subforum.

Best regards,
  Stefan Schießl
  Blockchain Projects BV

2
Dear BitShares Community,

we (Blockchain Projects BV and Ryan Fox) are happy to announce (finally) the renewal for HackTheDex:

https://www.bitshares.foundation/workers/2019-04-hackthedex

Abstract

Quote
HackTheDex bounty program was started in July 2018 and is consequently renewed now. Several critical reports have been submitted and fixed through HackTheDex, proof for its value and necessity. Those reports included several possibilities for chain halt and other severe attacks. An overview can be found here:

https://hackthedex.io/#/reports

BitShares is a decentralized exchange (DEX) built on top of delegated proof-of-stake (DPoS) blockchain technology. With all financial technology in the blockchain space, a major concern for users and traders is security.

If someone found a critical bug in the DEX, they might be tempted to exploit the bug, and attempt to steal funds from unsuspecting users. Without a public bug bounty system, hackers do not have an obvious path of disclosure for reporting their findings. They also do not have any incentive to share their exploits and techniques, rather than using them for personal gain.

With this proposal, we’d like to start a BitShares bug bounty program for security researchers and penetration testers (…aka hackers!) to disclose important security vulnerabilities they find within the BitShares core protocol, reference wallet, and related code repositories.

This proposal requires little funding as most of the budget can be transferred from the old worker .

Thanks for any feedback and your support,
  Blockchain Projects BV
  Stefan Schießl

3
Deploy and maintain independent BitShares infrastructure

Dear BitShares Community,

given the growth of the BitShares ecosystem, we (Blockchain Projects BV) have been providing a basic infrastructure with the just expired previous infrastructure worker.
That said, we would like to continue to provide the nodes and elastic search APIs that have been deployed with the last worker, the reference faucet has been moved to a new worker.

Read the full details here: https://www.bitshares.foundation/workers/2019-02-infrastructure

Voting for worker proposals: Votes can be done via the reference wallet. Visit Menu -> Votes -> Workers or enter your account name in the link https://wallet.bitshares.org/#/account/youraccountnamehere/voting

This worker proposal has id 1.14.164 and 201902-infrastructure.

Best Regards,
  Stefan Schießl
  Blockchain Projects BV

4
Dear BitShares Community,

we have carefully crafted a marketing proposal with limited budget to advance in that sections

https://www.bitshares.foundation/workers/2019-02-marketing-interviews-articles-and-visibility

Our aim is to have milestones that are tangible and measurable while being inclusive towards the community by allowing freelancer contributions. We believe we can leverage our extensive network into the BitShares Community  to come to profound decisions in the selection of external contributions.

Best regards,
  Blockchain Projects BV
  Stefan Schießl

5
Dear BitShares Community,

allow us to introduce a new BSIP that will enable off-chain activities that can be settled transparently on the blockchain, and implicitly enables the creation of savings accounts for the users that are locked a certain time period to enhance fund security.

For an easy read, please find the file here:
   https://github.com/blockchainprojects/bsips/blob/56_Managed_Vesting_Policies/bsip-0056.md

Any and all feedback are welcome, this BSIP is a draft so far, discussion will also be found in the respective pull request
   https://github.com/bitshares/bsips/pull/119

Best regards,
Stefan Schießl
Blockchain Projects BV

6
We at Blockchain Project B.V. have identified the need for an open source mobile wallet for quite
some time. There are a few apps in existence already. Some of them are in Java and open source,
others are closed-source.

A while ago, we went ahead and made an investment to develop a framework for android/ios phones
to work with the BitShares Platform. We explicitly chose for React Native so that Javascript developers
and/or react developers have it easy to get into app development for BitShares.

At this point, our plan is to Open Source first, and ask for funding of ongoing development (12 months).
The details are provided here:

     https://www.bitshares.foundation/workers/2018-10-mobile-sdk

Given my involvement and conflicts of interest through my position as proxy and committee member, I would like to
get a discussion about this going BEFORE the worker terms/conditions re frozen and put up for vote on chain.

So, please. Shoot your feedback!

7
Deploy and maintain independent BitShares infrastructure

Dear BitShares Community,

given the growth of the BitShares ecosystem, we (Blockchain Projects BV) have been providing a basic infrastructure with the just expired infrastructure worker (reports can be found here http://www.bitshares.foundation/workers/2017-12-infrastructure). The community has been contributing as well and the number of nodes for the reference wallet has been increased greatly.

That said, we would like to continue to provide the nodes that have been deployed with the last worker as well as the faucet for the reference wallet.

Read the full details here: http://www.bitshares.foundation/workers/2018-07-infrastructure

Voting for worker proposals: Votes can be done via the reference wallet. Visit Menu -> Votes -> Workers or enter your account name in the link https://wallet.bitshares.org/#/account/youraccountnamehere/voting

This worker proposal has id 1.14.108 and name 201807-infrastructure.

Update 27. July 2018:
Worker is active. Roadmap can be found here
https://github.com/blockchainprojects/bitshares-worker-infrastructure/blob/master/Roadmap_2018-07-infrastructure.pdf


Best Regards,
  Stefan Schießl
  Blockchain Projects BV

8
Dear BitShares Community,

We, Blockchain Projects BV, are proud to announce the initiation of listing the BitShares core token BTS with the Lykke exchange.

Contact to the Lykke team was established November 2017 and we have been negotiating since then to get BTS listed. We are in the process of completing the technical work as we speak. The BitShares Blockchain Foundation (BBF) was involved between Blockchain Projects BV and Lykke to get the required legal confirmation to list BTS, which was necessary since Lykke provides a direct FIAT on- and off-ramp. The BBF will continue to provide technical and economical descriptions to Lykke’s legal council in the next goal to explore the possibility of listing BitShares price-stable SmartCoins (e.g. bitUSD, bitEUR, see http://www.bitshares.foundation/smartcoins).

We see great benefits for the BitShares community and want to summarize the impact of the Lykke integration:
  • A FIAT on/off ramp for BTS without the need for Bitcoin
  • A potential FIAT on/off ramp for the price-stable SmartCoins

Thanks to Lykke, the integration module that is being developed for the listing, called
Bexi - BitShares Exchange Integration API,
will be open source and made available after the development is completed, reviewed and tested by Blockchain Projects BV.

Blockchain Projects BV
Stefan Schießl

9
Abstract

With the current design, the issuer of an asset can be changed with the active authority alone. However, this authority is also required for issuing new units of an asset/token. If this process wants to be automated, an active key needs to be stored on an internet-connected device. If compromised, an attacker can easily move the asset under his control with no way to back.

This proposal comes with two changes to the protocol:

    The current behavior of changing an assets' parameters will no longer allow to change the issuer.
    A new operation is introduced that allows to change the issuer of an asset but requires the owner authority of the issuer to sign that transaction.

Full BSIP
https://github.com/bitshares/bsips/blob/master/bsip-0029.md

Worker proposal
1.14.81

Payment
400bitUSD to cover the costs of setting up the worker proposal and the BSIP
The code is proudly sponsored by Blockchain Projects BV
Escrowed through BitShares Blockchain Foundation

10
We would like to let everyone know that our development team lead by @xeroc has
worked on a new feature that allows to claim BTS from the fee pool.

While we recognize that this can be seen as a minor contribution, we believe that
starting with baby steps first and establishing a reputation as a core development team
is the better approach and proposing significant changes right away.

The following contributions comes as a gift to the BitShares community and is released
under MIT:
https://github.com/bitshares/bitshares-core/pull/572/files

Whether the code is merged with bitshares-core to be released on a yet to be defined
hard fork date remains under the control of the core developers and the rest of the community.

Pages: [1]