Bitcoin encrypted paywall

Sell your files, images, notes or other digital goods protected by AES encryption in the browser.

https://bitaps.com/paywall

Bitcoin encrypted paywall tool, allows you to create payment lock on files or a text message where user need to pay the assigned amount of Bitcoins to access the content. File content, file names and all messages including descriptions are encrypted in the browser. The service does not have access to content on its servers, so your media data is completely protected with AES encryption. Service charge flat rate fee 0.0002 BTC for each sale. Forwarding the payment to the seller's address takes place within 1-3 confirmations of the bitcoin network. Files and media data under 200MB hosted for free within 1 year. Files greater than 200MB hosted for free for 72 hours.

The Paywall link has a built-in password. Encryption password is part of this link after # character. All web browsers use URL standard. According to this standard, the part of the URL after the # character is an optional fragment. This fragment is only used on the client side(navigation on page) and web browsers do not send this part of the link to the server. Paywall service never knows or gets a password for server-side content. Decryption occurs only on the client side in the browser.

Support email: support@bitaps.com
Telegram: https://t.me/bitapscom

Here is a link for a draft of a BIP for  compact probabilistic block filters alternative of BIP 158

https://github.com/bitaps-com/bips/blob/master/bip-block-batch-filters.mediawiki

https://github.com/bitaps-com/bips/blob/master/bip-mempool-transactions-filters.mediawiki

Summary:

- Block filters batching reduce total filter size. Total filters size  is smaller then BIP 158 at all total size savings  22% (3.36 GB vs 4.3 GB)
- Separation of filters by address type allows lite client not to download redundant information without compromising privacy.
- filter is deterministic  and could be committed as commitment in an coinbase transaction in future.
- unlocked ability to filter unconfirmed transaction for SPV nodes used BIP 157 instead of BIP 37 due privacy leak in BIP 37
- more bandwidth consumption reduced in contrast with transaction filters and downloading full blocks for affected addresses
- fully compatible for future consensus layer soft-fork to make block filters commitment one of the block validation rule


Any feedback or discussions are welcome

Just launched Bitcoin testnet faucet for developers.

Faucet url: https://tbtc.bitaps.com

Limits per IP address:

• 4 requests per 10 minutes
• Onetime limit 0.1 BTC

Send coins back, when you don't need them anymore: 2NBkWjz21BoT4abvAF5wsqnZAS7HA4LKrZe

Old standard transactions format included 3 types: P2PUBKEY, P2PKH, P2SH. After Segwit soft fork, we have got 2 additional types: P2WPKH and P2WSH.

If we compare cost of spending inputs (in bytes we write on HDD) for   P2PUBKEY, P2PKH and P2WPKH and  we got next values:

• P2PUBKEY  33 bytes public key(we do not consider uncompressed keys)  + signature 72 bytes = 105 bytes
• P2PKH        20 bytes public key hash + 33 bytes public key + 72 bytes signature = 125 bytes
• P2WPKH     20 bytes public key hash + 33 bytes public key + 72 bytes signature = 125 bytes

From this comparison we can conclude that P2PUBKEY the best for reduce blockchain size. We can save about 19% of spending input size. I understand that P2PKH give more
security in case we do not reuse address. In case we reuse address there are no advantages use P2PKH. We can observe quite frequent use of addresses repeatedly. For a certain range of tasks we not need extra security like P2PKH. Why in Segwit transaction types we don't have ability to use P2WPUBKEY as standard transaction?  This type of transaction help to reduce blockchain size in case user do not need/want use "no address reuse" security model? 20 bytes for each input this is good opportunity to save the size of blockchain.

Also I read this thread https://bitcointalk.org/index.php?topic=6430.0, what is the reason why bitcoin core developers do not want use public key recovery and save 33 bytes for each input?  If the concerns are related to performance, we can observe how the ethereum works and reaches about 1M tx per day (this is like 1M inputs per day in Bitcoin).

Today about 15 hours ago, was transaction malleability attack to bitcoin network. BIP 62 was accepted in 2014 but in 2017 miner BitClub mine transactions with negative S value in signature!    So BitClub gave the opportunity to this  attack get  success
 
We have bitcoin node with ability to save all events on bitcoin network.

Statistics on our bitcoin node:
   Total affected Transaction: 84335
   Success: 1405
 

Code:

9ab1d8ede94b8997c526680c197ed6cf1d2004845f1a409645c36c52d5c3fefa
  >>>  00070d799ae941cd60fc686802afba8609f637687df8714c9b29c03600a7559b block 456545 miner BitClub
6f1f6740eb0eaa7db013461f497e4fdc39594ab506c70708ed6969c25e9cbae0
  >>>  f889938e3878a9836caa558c926bc2b05353cf29eb7f8ebbdffe0a5af80af5a4 block 456545 miner BitClub
924e59a5d70f2e8928a1dfdd01cab476caebf5773b001d06ad87d4619ff8674e
  >>>  785b2856106170b5ef462b35deae83879bb9e3fd282b3e5face8fe0d9ec17285 block 456545 miner BitClub
00fba70e71336d78c52cda58c252a836d1d860c69e54840fb85f6f9e947eef75
  >>>  2000e4a79fb534563f361a5a3f031c3db2d87a886b072b6ba68587ebbebc6198 block 456545 miner BitClub
71bad5a7eb5693e1787572c62ce3fe81be57907c9a67e5b67df32615b6fcc564
  >>>  783a6b069abb42818ef942832b8aad689c52c9e054572a8e5c5f402b41b1d35e block 456545 miner BitClub
5ad4bd91dc3b1588a5dd3fc880109400a467316114b64c093ba2624e6d9bfa28
  >>>  5e60913b376ce04a526dfd26ec60b5c0e86e5cbf61b0cc77ad170b35240dd313 block 456545 miner BitClub
c3d73f073d9efb1e6b5f83de13415e8f76763a1526c58283ec887a0f6b54a987
  >>>  9f4fd7345061fc567eca2807aa7f655696a0fcd0b4c039e597978ec935a8c4c4 block 456545 miner BitClub
bc256939a84a8a7d25e1e3f79b9cdc61f8f84cb1746371b6e75076f548bca6b1
  >>>  ab1f20f7785137012de35e81709b2172c0d56af4949e53bfed9ddea9ddfb9527 block 456545 miner BitClub
304210e71da43a2f64410568b0473a1652da245e15eaccf42526636ced50be10
  >>>  04916551d68114586f22f6fe5e9cc73497f6b91fd440c764301437fc069afe69 block 456545 miner BitClub

 
 
Full list of successfully attacked transactions http://pastebin.com/KGYpqPta
 

Приветствую всех

https://bitaps.com - Bitcoin процессинг и Bitcoin эксплорер.
 

Плюсы работы с нашей компанией:
1) мы не имеем возможности блокировать кошельки клиентов (в отличии от Bitpay, Blockchain info, Coinbase...), так что ваши деньги будут в полной сохранности
2) мы работаем по всему миру без ограничений по странам
3) нам всё равно что процессить, главное пишите код правильно

Ссылка на API: https://bitaps.com/api/
Здесь есть удобный конструктор запросов и кода для PHP, Python, cURL.

Если потребуется помощь, пишите нам admin@bitaps.com или support@bitaps.com

[src/script/interpreter.cpp]

Today I reading bitcoind src, and try to find out where is pubkey script executed when node received new block with transaction, at example transaction from new block may not be exist in mempool

    Find function that execute script:

    https://github.com/bitcoin/bitcoin/search?utf8=%E2%9C%93&q=EvalScript

        src/script/interpreter.cpp in this file source code of EvalScript function

    Used only in this 2 files:

        src/policy/policy.cpp

        src/script/sign.cpp

    Review sign.cpp

Evalscript -> CombineSignatures -> /src/bitcoin-tx.cpp: MutateTxSign -> MutateTx -> CommandLineRawTx -> main

This functions used when we create ne transactions

    Review policy.cpp

Evalscript -> AreInputsStandard -> /src/main.cpp: AcceptToMemoryPool

AcceptToMemoryPool

    src/main.cpp later

    src/wallet/wallet.cpp -> CommitTransaction - this is create own transaction functional

    src/rpcrawtransaction.cpp -> sendrawtrnsaction - rpc function send rawtx

    src/txmempool.cpp -> no calls only comments

Last one is src/main.cpp

AcceptToMemoryPool -> ProcessMessage on message "tx" , new single tx to pool received AcceptToMemoryPool -> DisconnectTip

DisconnectTip -> InvalidateBlock invaludate block and send all transaction back to pool with all verifications and script eval

DisconnectTip -> ActivateBestChainStep :

  // Disconnect active blocks which are no longer in the best chain.
bool fBlocksDisconnected = false;
while (chainActive.Tip() && chainActive.Tip() != pindexFork) {
    if (!DisconnectTip(state))
        return false;
    fBlocksDisconnected = true;
}

If we have orphan tak out transactions from orphan to pool with all verifications

NO more other links found

From this I can conclude that in case node with bitcoind received new block with transactions that not in mempool we add this tx to blockchain without pubkeyscript execute.


Consequently if same "honest" miner include tx with invalid script, at example incorrect signature that spent same one coins, all bitcoind nodes add it to blockchain without eval script and not detect this

It is not posible to be true! Where is my error?

Сегодня ковырял исходники bitcoind, пытался найти где при добавлении блока происходит исполнение скрипта транзакции

1. Делаем поиск функции которая исполняет скрипт

          https://github.com/bitcoin/bitcoin/search?utf8=%E2%9C%93&q=EvalScript

               src/script/interpreter.cpp   здесь находится сам код функции

               используется только в этих 2 файлах

                   src/policy/policy.cpp

                   src/script/sign.cpp

2. Смортим sign.cpp
    
Evalscript -> CombineSignatures -> /src/bitcoin-tx.cpp: MutateTxSign -> MutateTx -> CommandLineRawTx -> main далее совпадений нет, сдесь явно нет пути вызовов при добавлении блоков или транзакций

3. Смотрим policy.cpp

Evalscript -> AreInputsStandard -> /src/main.cpp: AcceptToMemoryPool

AcceptToMemoryPool :
 
    src/main.cpp            
    src/wallet/wallet.cpp   -> CommitTransaction    -  здесь реализация локального кошелька. исполнение скрипта происходит при создании своей транзакции
    src/rpcrawtransaction.cpp -> sendrawtrnsaction - здесь рпс функционал, послать сырую транзакцию
    src/txmempool.cpp  -> нет вызова, участвует в коментарии

Остается только src/main.cpp

  AcceptToMemoryPool -> ProcessMessage  при обработке соощения tx, то есть поступление отдельной транзакции из сети и добавления ее в пул
  AcceptToMemoryPool -> DisconnectTip
 
   DisconnectTip -> InvalidateBlock    сделать блок невалидным и транзакции из блока вернуть в пул при возрате исполняются проверки и скрипты
                                
   DisconnectTip -> ActivateBestChainStep :

  // Disconnect active blocks which are no longer in the best chain.
    bool fBlocksDisconnected = false;
    while (chainActive.Tip() && chainActive.Tip() != pindexFork) {
        if (!DisconnectTip(state))
            return false;
        fBlocksDisconnected = true;
    }
 сдесь в случае если образовался орфан мы из этого орфана выкидываем транзы обратно в пул со всеми проверками


Больше никаких связей с функцией исполнения скрипта нет

Из этого я могу сделать вывод что в случае если приходит новый блок и он в своем составе содержит транзакцию которой у нас нет в мемпуле то мы добавляем эту транзакцию в составе
данного блока в blockchain без исполнения sigscript + Pubkeyscript.

Следовательно мы добавляем транзакцию с потенциально невалидным скриптом. К примеру несходится сигнатура и мы тратим чужую монету и создаем свою.
Следовательно непорядочный майнер может это осуществить и вся сеть примет этот блок так как реальное исполнение скрипта непроизошло и ноды с bitcoind  этого незаметят

Где я ошибаюсь ? это же неможет быть правдой?




  
  

I am trying to collect all infromation about adding and verification transaction into Blockchain.


Could any experts in this question verify that collected information is actual and correct? Thank you

Node add transaction to pool policy


Blockchain transaction validation rules



Fixed  both schemas, thank  to yakuza699 and amaclin for help and explanations!

[Bitaps.com]

Bitaps.com

Just started new project. Online cryptocurrency wallet. Supported coins: Bitcoin, Litecoin, Dogecoin. Other type of coins and more features will be developed soon.

Please try our first release. We want to hear feedback from users and ready to develop more features that you will wish or offer.

Web site:  http://bitaps.com


If you have any questions, support queries or offers, please feel free to contact us at: support@bitaps.com