Skip to content

Conversation

genjix
Copy link

@genjix genjix commented Apr 16, 2011

  1. bitcoind -naming-password=hello
  2. bitcoind publickey

    copy this output to clipboard

  3. login to http://109.75.176.109

    paste public key and click 'Update'

  4. add a new nickname
  5. bitcoind updatename myname@109.75.176.109

Now someone else can run:

bitcoind send genjix@109.75.176.109 2

Your keypair for altering your nickname is stored in .bitcoin/keypair.rsa

Forum post: http://www.bitcoin.org/smf/index.php?topic=5938.0

genjix and others added 30 commits March 6, 2011 23:38
Should be placed in the top level dir during release.
…o stop the attack vector of tricking someone into getting your bitcoin addresses which is actually something that can execute code due to a vulnerability in their server software.
@genjix
Copy link
Author

genjix commented Apr 16, 2011

There was a privacy concern raised before about the servers being able to monitor who pushes addresses and who fetches addresses being able to infer IP addresses to Bitcoin addresses by means of the blockchain. After much consideration and chatting with topi`, I decided on the maxim that there's a trade-off between user inconvenience and anonymity at some point.

Educated users should be using Bitcoin addresses for large amounts and this naming protocol as a convenience method for small amounts.

@jgarzik
Copy link
Contributor

jgarzik commented Apr 18, 2011

Yowza! That is a long history :)

For ease of reviewing and clean git history, we request that you rebase your pull requests once the history gets long like this.

Closing pull request for administrative reasons -- but you are welcome to reopen at any time, with a rebased and review-friendly set of commits.

Thanks for your continued contributions.

@jgarzik jgarzik closed this Apr 18, 2011
zathras-crypto added a commit to zathras-crypto/omnicore that referenced this pull request Aug 12, 2015
Add hidden RPC command to activate features
rebroad pushed a commit to rebroad/bitcoin that referenced this pull request Dec 7, 2016
ptschip pushed a commit to ptschip/bitcoin that referenced this pull request Dec 25, 2016
Add emergent consensus to sigop and transaction size
destenson pushed a commit to destenson/bitcoin--bitcoin that referenced this pull request Nov 18, 2017
0a5ef95 [Budget] Add log for removed budget proposals (Mrs-X)
d323160 [Consensus] Don't pass the genesis block through CheckWork (Fuzzbawls)
3679a8c [Trivial] Use LogPrint for repetitive budget logs (presstab)
3b239c1 [Qt] Avoid OpenSSL certstore-related memory leak (Jon Spock)
feac301 [Wallet] Look at last CoinsView block for corruption fix process (presstab)
dfa017f [Wallet] Reduce usage of atoi to comply with CWE-190 (Fuzzbawls)
fd1d3c8 [Qt] Adds base CSS styles for various elements, to prevent bleed-through of system color theme. (Mrs-X)
036034e Remove Keepass code due to Valgrind warnings (Spock)
f23e5bb Squash valgrind warnings for groestl by initing array (presstab)
779894f [QT] Fix false flags for MultiSend notification when sending transactions (presstab)
fb49d9e [RPC] Require password when using UnlockAnonymizeOnly (presstab)
07f1f88 [Qt] Remove trading window (Spock)
d573fd5 [QT] Fix Overview Page Balances when receiving (Mrs-X)
08b8cae [UI] Show path to wallet.dat in wallet-repair tab (Mrs-X)
7056e31 [UI] Edit masternode.conf in Qt-wallet (Mrs-X)
8d4f7a3 [Docs] Add GitHub Issue template and Contributor guidelines (Fuzzbawls)
d702bb9 [RPC] Add `getstakingstatus` method (Fuzzbawls)

Tree-SHA512: b06d8cf845d2bc8e165e42295683e5e27eb56e1aeff213a6c432853defb193de92473250f51a82bc56410c138cd78f166902d56abb31aed0c23300af9699df73
classesjack pushed a commit to classesjack/bitcoin that referenced this pull request Jan 2, 2018
Qt wallet PoS features - Part 1 (QTUMCORE-70)
KolbyML pushed a commit to KolbyML/bitcoin that referenced this pull request Aug 1, 2020
jonasschnelli added a commit that referenced this pull request Jan 11, 2021
…data layer violation

b3e9bca qt, refactor: Drop no longer used PeerTableModel::getNodeStats function (Hennadii Stepanov)
49c6040 qt: Use PeerTableModel::StatsRole (Hennadii Stepanov)
35007ed qt: Add PeerTableModel::StatsRole (Hennadii Stepanov)

Pull request description:

  This PR allows to access to the `CNodeCombinedStats` instance directly from any view object.

  The `PeerTableModel::getNodeStats` member function removed as a kind of layer violation.

  No behavior changes.

  Also other pulls (bugfixes) are based on this one: #18 and #164.

ACKs for top commit:
  jonatack:
    Tested re-ACK b3e9bca per `git range-diff ae8f797 4c05fe0 b3e9bca`
  promag:
    Code review ACK b3e9bca.
  jonasschnelli:
    utACK b3e9bca

Tree-SHA512: 6ba50d5dd2c0373655d491ce8b130c47d598da2db5ff4b00633f447404c7e70f8562ead53ddf166e851384d9632ff9146a770c99845c2cdd3ff7250677e4c130
rajarshimaitra pushed a commit to rajarshimaitra/bitcoin that referenced this pull request Mar 23, 2021
Lightning-specific encoding and encoding-related types
hebasto added a commit that referenced this pull request Jul 5, 2021
…-sort Peers table

986bf78 qt: Emit dataChanged signal to dynamically re-sort Peers table (Hennadii Stepanov)

Pull request description:

  [By default](https://doc.qt.io/qt-5/qsortfilterproxymodel.html#details), the `PeerTableSortProxy`
  > dynamically re-sorts ... data whenever the original model changes.

  That is not the case on master (8cdf917) as in ecbd911 (#164) no signals are emitted to notify about model changes.

  This PR uses a dedicated [`dataChanged`](https://doc.qt.io/qt-5/qabstractitemmodel.html#dataChanged) signal.

  Fixes #367.

  An alternative to #374.

ACKs for top commit:
  jarolrod:
    ACK 986bf78

Tree-SHA512: dcb92c2f9a2c632880429e9528007db426d2ad938c64dfa1f1538c03e4b62620df52ad7daf33b582976c67b472ff76bc0dae707049f4bbbd4941232cee9ce3d4
rajarshimaitra pushed a commit to rajarshimaitra/bitcoin that referenced this pull request Aug 5, 2021
WIP: Development Environment: Docker and docker-compose setup
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants