Good idea. On the flip side, I don't know that we need any more alt coins...  |
|
|
|
This is increasing the barrier to entry & risk for new merchants and bitcoin services, and making it harder to gain the trust of users.
Increasing barrier and risk? If you site is secured, you have no risk. If you site is not secure, YOU are causing the risk, no people probing your servers. This is more than a bitcoin maturity issue, the security & trust problems are larger than we want to admit. We need evolutionary security & trust changes around bitcoin to make this thing happen.
Incorrect. You cannot base the security of your ecommerce website on "trusting" everyone not to attack it even though it's vulnerable. I'll put it simply. It is the site owner's responsibility to fully secure their site. If they do not, it *will* be compromised sooner or later. This has nothing to do with Bitcoin and everything to do with website owners being responsible. |
|
|
|
|
Thanks for posting this giga!
|
|
|
|
|
I must say that both Goat/Chaang AND Bitcoin Magazine/its representatives have been acting in an extremely childish manner. I thought Bitcoin Magazine would be something to look forward to. Maybe not.
|
|
|
|
This paper does not matter IMHO.
Any reason? |
|
|
|
....
H? I think your message got truncated. |
|
|
|
Shadow, I wanted to follow up on a recent conversation I had with you concerning Armory and transaction fees. I made a mistake in my initial assessment of what I could do with it. I have implemented all the tx fee calculations and exactly when they need to be applied. The default behavior of Armory is to let you select 0.0 fee, but if the calculation determines you need more, you either have to increase the fee, or cancel. I had decided to put in an "Override Minimum Fee" setting that you would have to change by hand, but it could be done. This was all implemented and the dialogs are even created and work. The problem is that since Armory connects through localhost-Satoshi-client, transactions that "need" a fee but don't have them, will not get forwarded. Thus, even though the network is full of nodes that will take zero-fee txs, Armory only has one peer, and the forced-zero-fee transactions are DOA. It seems, the only way for Armory to do this, is if this fork is used along with the over-ride min fee option (though, I haven't tried it). In the future, I will have some kind of independent networking that will allow me to sidestep this problem. Until then, I can't live up to my promise of supporting forced zero-tx fees! You could work around it though. When you have a forced zero-fee tx, instead of just passing the tx to the local bitcoind, send a getaddr message to the local bitcoind, parse the addresses received, then connect to all of those nodes and broadcast the tx to them. If I understand correctly, you need the local bitcoind for the blockchain, but there's no reason you have to use it exclusively for broadcasting transactions. |
|
|
|
|
Good work eto. I think deterministic wallets should be considered for the reference implementation as well.
|
|
|
|
Hmmm, is he Catholic?
You need to ask?  After reading some of that more closely, no. |
|
|
|
crap you insert into the block headers
example? Most of (but a few not e.g. look for his name) Eligius/Benedictus Deus. Benedictum Nomen Sanctum eius.
Eligius/Benedictus Deus. Benedictum Nomen Sanctum eius.
***************************************************
Benedictus Iesus Christus, verus Deus et verus homo.
Benedictum Nomen Iesu.
Benedictum Cor eius sacratissimum.
Benedictus Sanguis eius pretiosissimus.
Benedictus Iesus in sanctissimo altaris Sacramento.
Benedictus Sanctus Spiritus, Paraclitus.
Benedictus Sanctus Spiritus, Paraclitus.
Benedicta excelsa Mater Dei, Maria sanctissima.
Benedicta sancta eius et immaculata Conceptio.
Benedicta sancta eius et immaculata Conceptio.
Benedicta eius gloriosa Assumptio.
Benedictum nomen Mariae, Virginis et Matris.
Benedictum nomen Mariae, Virginis et Matris.
Benedictus sanctus Ioseph, eius castissimus Sponsus.
Benedictus Deus in Angelis suis, et in Sanctis suis. Amen.
In nomine Patris et Filii et Spiritus Sancti. Amen.
O my God, I am heartily sorry for having offended Thee and I detest all my sins...
O my God, I am heartily sorry for having offended Thee and I detest all my sins...
Eye'm the strongest!
...because of Thy just punishments, but most of all because they offend Thee, ...
...my God, who art all good and deserving of all my love.
I firmly resolve, with the help of Thy grace, to sin no more...
I firmly resolve, with the help of Thy grace, to sin no more...
...and avoid the near occasions of sin. Amen.
O my God! I firmly believe that Thou art one God in three Divine persons, ...
O my God! I firmly believe that Thou art one God in three Divine persons, ...
...Father, Son, and Holy Ghost; I believe that Thy Divine Son became man, ...
...and died for our sins, and that he will come to, judge the living and the dead.
I believe these and all the truths which the Holy Catholic Church teaches, ...
...because Thou hast revealed them, who canst neither deceive nor be deceived.
O my God! relying on Thy infinite goodness and promises, ...
...I hope to obtain pardon of my sins, the help of Thy grace, ...
...and life everlasting, through the merits of Jesus Christ, my Lord and Redeemer.
...and life everlasting, through the merits of Jesus Christ, my Lord and Redeemer.
O my God! I love Thee above all things, with my whole heart and soul, ...
...because Thou art all-good and worthy of all love.
...because Thou art all-good and worthy of all love.
I love my neighbor as myself for the love of Thee.
I forgive all who have injured me, and ask pardon of all whom I have injured.
I forgive all who have injured me, and ask pardon of all whom I have injured.
I forgive all who have injured me, and ask pardon of all whom I have injured.
O my Jesus, forgive us our sins, save us from the fires of Hell, ...
...lead all souls to Heaven, especially those in most need of Thy mercy.
I confess to Almighty God, to blessed Mary ever Virgin, ...
... to blessed Michael the Archangel, to blessed John the Baptist, ...
... to the holy Apostles Peter and Paul, and to all the Saints, ...
... that I have sinned exceedingly, in thought, word, and deed, ...
... through my fault, through my fault, through my most grievous fault.
Therefore I beseech blessed Mary ever Virgin, blessed Michael the Archangel, ...
... blessed John the Baptist, the holy Apostles Peter and Paul, ...
... and all the Saints to pray to the Lord our God for me. Amen.
St. Michael the Archangel, defend us in battle; be our safeguard against ...
St. Michael the Archangel, defend us in battle; be our safeguard against ...
... the wickedness and snares of the Devil. May God rebuke him, ...
... we humbly pray, and do Thou, O Prince of the Heavenly Host, ...
... we humbly pray, and do Thou, O Prince of the Heavenly Host, ...
... we humbly pray, and do Thou, O Prince of the Heavenly Host, ...
... we humbly pray, and do Thou, O Prince of the Heavenly Host, ...
... by the power of God, cast into Hell, Satan and all the other evil spirits, ...
... who wander throughout the world, seeking the ruin of souls. Amen.
Angel of God, my guardian dear, to whom His love commits me here, ...
... ever this night be at my side, to light and guard, to rule and guide. Amen.
Ave Maria, gratia plena, Dominus tecum. Benedicta tu in mulieribus, ...
... et benedictus fructus ventris tui, Iesus. Sancta Maria, Mater Dei, ...
... et benedictus fructus ventris tui, Iesus. Sancta Maria, Mater Dei, ...
... et benedictus fructus ventris tui, Iesus. Sancta Maria, Mater Dei, ...
... ora pro nobis peccatoribus, nunc, et in hora mortis nostrae. Amen.
Salve, Regina, mater misericordiae: vita, dulcedo, et spes nostra, salve.
Ad te clamamus exsules filii Hevae. Ad te suspiramus, gementes et flentes ...
Ad te clamamus exsules filii Hevae. Ad te suspiramus, gementes et flentes ...
... in hac lacrimarum valle. Eia, ergo, advocata nostra, illos tuos ...
... misericordes oculos ad nos converte. Et Iesum, benedictum fructum ...
... ventris tui, nobis post hoc exsilium ostende. O clemens, O pia, ...
... O dulcis Virgo Maria. Ora pro nobis, sancta Dei Genetrix.
kLhLUKE-JR IS A PEDOPHILE! Oh, and god isn't real, sucka. Stop polluting the blockchain with your nonsense.
Ut digni efficiamur promissionibus Christi. Amen.
Pater noster, qui es in caelis, sanctificetur Nomen tuum. Adveniat regnum tuum.
Pater noster, qui es in caelis, sanctificetur Nomen tuum. Adveniat regnum tuum.
Fiat voluntas tua, sicut in caelo et in terra. Panem nostrum quotidianum ...
... da nobis hodie, et dimitte nobis debita nostra sicut et nos dimittimus ...
... debitoribus nostris. Et ne nos inducas in tentationem, sed libera nos a malo.
Domine Iesu Christe, Filius Dei, miserere me peccatorem!
We adore Thee, O Christ, and we bless Thee;
We adore Thee, O Christ, and we bless Thee;
because by Thy holy Cross Thou hast redeemed the world.
May the Holy Trinity be blessed.
Christ conquers! Christ reigns! Christ commands!
O Heart of Jesus, burning with love for us, inflame our hearts with love for Thee.
O Heart of Jesus, burning with love for us, inflame our hearts with love for Thee.
O Heart of Jesus, I place my trust in Thee.
O Heart of Jesus, all for Thee.
O Heart of Jesus, all for Thee.
Most Sacred Heart of Jesus, have mercy on us.
O God, have mercy on me, a sinner.
Teach me to do Thy will, because Thou art my God.
O Lord, increase our faith.
O Lord, save us, we are perishing.
O Lord, increase our faith.
O Lord, save us, we are perishing.
O Lord, increase our faith.
O Lord, save us, we are perishing.
O Lord, increase our faith.
O Lord, save us, we are perishing.
May the Most Blessed Sacrament be praised and adored forever.
Jesus, meek and humble of heart, make my heart like unto thine!
Holy Trinity, one God, have mercy on us!
Gloria Patri, et Filio, et Spiritui Sancto. Sicut erat in principio, ...
... et nunc, et semper, et in saecula saeculorum. Amen.
... et nunc, et semper, et in saecula saeculorum. Amen.
Feast of Saint Joseph Calasanctius, confessor
FFS Luke-Jr leave the blockchain alone!
Oh, and god isn't real
Feast of Saint Augustine, bishop, confessor, and doctor
Feast of Saint Hermes, martyr
Commemoration of the Beheading of Saint John the Baptist
Commemoration of the Beheading of Saint John the Baptist
Commemoration of the Beheading of Saint John the Baptist
Commemoration of the Beheading of Saint John the Baptist
Commemoration of the Beheading of Saint John the Baptist
Commemoration of the Beheading of Saint John the Baptist
Commemoration of the Beheading of Saint John the Baptist
Commemoration of the Beheading of Saint John the Baptist
Commemoration of the Beheading of Saint John the Baptist
Commemoration of the Beheading of Saint John the Baptist
The harvest indeed is great, but the labourers are few. Pray ye therefore...
The harvest indeed is great, but the labourers are few. Pray ye therefore... (I removed all but a few that aren't from Eligius) Hmmm, is he Catholic? Edit: I guess that goes without saying.... |
|
|
|
The limitation of Bitcoin is that the block chain is only aware of the total hashing power, not individual miners, and thus can only adjust accordingly. P2Pool protocol chain is sort, and is easy to change, and each instance of P2Pool is aware of both the pool hashing power and each instance's local hashing power.
Would it be possible to just change the algorithm from adjusting difficulty to make a pool block every ten seconds based on overall pool hashing power, to one that bases it on the fraction of your hashing power compared to the overall pool? Have the difficulty start out at average, and as you mine, every thirty minutes recalculate your local difficulty based on reported hashing power, so that strong miners get increased difficulty and fewer shares and weak miners get more?
Or is this too difficult due to all blocks in the chain needing to be the same, or risky due to being easily hacked?
Currently shares are all the same because (your payout) = (your shares) / (total last n shares). While you could make shares variable in difficulty and make it (your payout) = (sum of your shares difficulty) / (total sum of last n shares difficulty) it doesn't get around the ophan problem. Bitcoin rarely has orphaned blocks because the round time is ~600 seconds. The shorter the round time the more likely two entities on the network find solution at roughly the same time and one of them gets orphaned. P2pool compromises between share difficulty & orphan rate by using a 10 second round time. It sets difficulty so someone will find a share roughly 10 seconds (and hopefully most of the time that "solution") can be shared to everyone else to avoid duplicated work in time. So to avoid higher orphan rate you still need the average share time to be ~10 seconds. You could within reason allow smaller miners to use lower difficulty and larger miners to have higher difficulty but the average must still work out to ~1 share per 10 seconds. So that solution has two problems: a) the amount share difficulty can be vary is not much and if most miners are small it is very little at all. b) larger miners would be accepting higher variance in order to give smaller miners lower variance. Something for nothing. Unlikely they will do that. The way I see it there are four decentralized solutions: multiple p2pools, merged share chain, dynamic p2pools, sub-p2pools.multiple p2pools.The simplest solution is to simply start a second p2pool. There is no reason only one has to exist. Take the source code and modify it so the "alternate p2pool can be identified" and start one node. Node can join using modified client. Eventually client could be modified to have user indicate which instance of the network to join or even scan all instances and give user the option. If the two pool gets too large they also could be split. The disadvantage is that each split requires migration and that requires people to look out for the good of the network. For example 3 p2pools with 10GH, 20GH, and 2.87TH/s isn't exactly viable. -------------------------------------- merged share chainIn Bitcoin there can only be "one block" which links to the prior block. The reason why is it is used to prevent double spends. Double spend isn't as much of a problem in p2pool. Sure one needs to ensure that workers don't get duplicate credit but that can be solved without a static "only one" block-chain. Modifying the protocol to allow multiple branches at one level would seem to be possible. Since this would allow oprhans to be counted (within reason) it would be possible to reduce the share time. For example a 1 TH/s p2pool with a 2 second share time would have no higher difficulty than a 200 GH/s p2pool with 10 second share time. There likely are "gotchas" which need to be resolved but I believe a sharechain which allows "merging" is possible. -------------------------------------- dynamic p2pool.Building upon that idea of multiple p2pools the protocol could be expanded so that a new node queries a p2pool information net and gets statuses of existing p2pools. The network assigns new nodes where they best optimize the balance of the network. If the protocol enforces this pool assignment then there is no human gaming involved and the pools will be relatively balances. As pools grow or shrink they can be split or combined with other pools by the protocol. Some simulation would be needed to find the optimal balance between share variance and block variance. The network could even intentionally allow variance in pool size and share time. Larger pools with high difficulty and large share time to accommodate very large miners and smaller pools with lower difficulty to provide optimal solution for smaller individual miners. -------------------------------------- sub p2poolsImagine the p2pool forming a "backbone" and for max efficiency the share time would be longer. Say 1 share per 60 seconds instead of 10 (difficulty goes up by factor of 6). At 1TH/s that is ~12,000 difficulty (which is high but not as high as block difficulty of 1.3 million). Due to 12K+ difficulty the only participants on this backbone are a) major hashing farms, b) conventional pools, and c) sub p2pools. You notice I said conventional pools. Conventional pools which submit valid shares to p2pool are less of a security risk to Bitcoin than opaque proprietary poools. For smaller miners who wish a fully decentralized solution they could form/join "sub-p2pools". These pools could be tuned for different speed miners to provide an optimal balance between block difficulty and share difficulty. They would maintain a sub-p2pool level share chain and use that to set the reward breakout for the subpool. When the one node in the subpool solves a "master p2pool" difficulty share (12K in above example) it submits it to the main pool (which updates the ultimate reward split to include the subpool current split for that share). subpools could be created manually (Rassah small miner subpool), or eventually dynamically by an protocol similar to the second solution. This requires a modest change to the existing p2pool (which would form the backbone). Currently 1 share can only be assigned to 1 address. To make sub-p2pools possible it would need to be possible to include an address list and distribution % for 1 share. -------------------------------------- Note: these ideas aren't fleshed out. Likely someone can point out issues and areas where the explanation is incomplete. They are more designed as a thought exercise to look a potential avenues for expanding p2pool to handle potentially someday 51% of network hashing power (at which point an internal 51% attack becomes impossible). Obviously these are complex ideas which will take time to implement. I believe that "front ends" are preferable to small miners going back to deepbit and could act as a bridge to transition p2pool from 250GH/s to 1TH/s+ while more decentralized solutions are developed. forrestv, are you considering acting on any of these ideas? What are you current thoughts on this? |
|
|
|
watching...
nothing really has come of this... p2pool us awesome and is slowly growing but we need a second option. i have btc if i can get someone to make it... maybe even give the coder .5% for a few months or something as a bonus... Why don't you talk directly with forrestv? He might be amenable to creating a second p2pool, and/or acting on some of the ideas in the p2pool thread about ways to spin off alternate or sub p2pools. |
|
|
|
crap you insert into the block headers
example? |
|
|
|
Your anonymous cash deposit might not be so anonymous if they can link the deposit to a specific date/time and get surveillance camera data.  exactly, and even if you were able to hide your face, your gait is often uniquely identifiable... so you know, jump around like a chimp to throw them off. Hide you face, disguise you gait, and they'll still be able to get a DNA match from a hair that falls to the floor as you clearly scratch the back of your head on camera.... |
|
|
|
Would it be possible to put a block explorer into Armory?
This would be a good bit of functionality. On the offline computer, Armory will detect no internet and go into "offline mode."
Might be a nice idea to have a way of turning on "offline mode" even if you have an internet connection. |
|
|
|
Kk but it would seem more attractive to Litecoin CPU miners as there is no merged mining for that yet so all or most of the Litecoin CPU miners would likely adopt it pretty fast?
Why would it be more attractive? If you and merge-mine 2 chains (BTC and NMC), you can merge-mine 5 or 10. I don't see the point. |
|
|
|
|
I think this is an excellent idea. Watching.
|
|
|
|
I think your find it difficult to find miners as a lot of people have already adopted merged mining on Bitcoin with Namecoin. If you was to do merged mining with Litecoin CPU miners your not competing for new miners from anywhere and if you approach the Litecoin community and the major pools I'm sure there all be happy to merge your mining with theirs when your ready to start. This will lower the chance of a 51% attack.
You can merge-mine with more than 2 block chains. There's no reason people who are merge mining Bitcoin and Namecoin currently can't add an additional chain. This was already done with Devcoin as well. So as far as mining goes, there's no competition with Namecoin. |
|
|
|
|
Just finished reading the paper. You have some very, very good ideas. One thing I will mention, is I encourage you to carefully consider the benefits of merged mining with Bitcoin before discarding the idea.
Namespaces-- It might be a good idea to have namespaces and allow for sub-namespaces. This way you could have one namespace per "service" (Tor, I2P, a new service in direct competition with ICANN addresses, etc), and then each service can have sub-namespaces which would be analogous with the TLDs we currently have with ICANN.
|
|
|
|
|
Show Posts
